On Thu, 3 Oct 2024 21:17:09 +0000 Edward Liaw <edl...@google.com> wrote:
> 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. > > Updated the synchronization primitive to use pthread_barrier instead of > atomic_bool. > > Applied the same fix to the wp-fork-with-event test. > > Edward Liaw (2): > selftests/mm: replace atomic_bool with pthread_barrier_t > selftests/mm: fix deadlock for fork after pthread_create on ARM These fixes have different Fixes: targets, which might cause backporting issues - some kernels might end up with one patch and not the other. Was this intended? Is it OK?
