diff options
| author | Edward Liaw <[email protected]> | 2024-10-18 17:17:22 +0000 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2024-10-29 04:40:40 +0000 |
| commit | 5bb1f4c9340e01003b00b94d539eadb0da88f48e (patch) | |
| tree | 8cd207f8152864a2153396dcef51c273ecc7c3aa /drivers/acpi/cppc_acpi.c | |
| parent | tools: testing: add expand-only mode VMA test (diff) | |
| download | kernel-5bb1f4c9340e01003b00b94d539eadb0da88f48e.tar.gz kernel-5bb1f4c9340e01003b00b94d539eadb0da88f48e.zip | |
Revert "selftests/mm: fix deadlock for fork after pthread_create on ARM"
Patch series "selftests/mm: revert pthread_barrier change"
On Android arm, pthread_create followed by a fork caused a deadlock in
the case where the fork required work to be completed by the created
thread.
The previous patches incorrectly assumed that the parent would
always initialize the pthread_barrier for the child thread. This
reverts the change and replaces the fix for wp-fork-with-event with the
original use of atomic_bool.
This patch (of 3):
This reverts commit e142cc87ac4ec618f2ccf5f68aedcd6e28a59d9d.
fork_event_consumer may be called by other tests that do not initialize
the pthread_barrier, so this approach is not correct. The subsequent
patch will revert to using atomic_bool instead.
Link: https://lkml.kernel.org/r/[email protected]
Link: https://lkml.kernel.org/r/[email protected]
Fixes: e142cc87ac4e ("fix deadlock for fork after pthread_create on ARM")
Signed-off-by: Edward Liaw <[email protected]>
Cc: Ryan Roberts <[email protected]>
Cc: Peter Xu <[email protected]>
Cc: Shuah Khan <[email protected]>
Cc: <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'drivers/acpi/cppc_acpi.c')
0 files changed, 0 insertions, 0 deletions
