linux-kernel - Re: [PATCH 0/2] selftests/mm: fix deadlock after pthread

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20241004165452.a28856a9404a5a67d6fd201d@linux-foundation.org>
Date: Fri, 4 Oct 2024 16:54:52 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Edward Liaw <edliaw@...gle.com>
Cc: linux-kselftest@...r.kernel.org, Shuah Khan <shuah@...nel.org>, Lokesh
 Gidra <lokeshgidra@...gle.com>, Peter Xu <peterx@...hat.com>,
 linux-kernel@...r.kernel.org, kernel-team@...roid.com, linux-mm@...ck.org
Subject: Re: [PATCH 0/2] selftests/mm: fix deadlock after pthread_create

On Thu,  3 Oct 2024 21:17:09 +0000 Edward Liaw <edliaw@...gle.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?