linux-kernel - Re: [PATCH 0/3] selftests/mm: revert 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 for Android: free password hash cracker in your pocket

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

Message-Id: <20241018141323.e1c7e0a7312ffd7b92c8f4c5@linux-foundation.org>
Date: Fri, 18 Oct 2024 14:13:23 -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>, Peter Xu
 <peterx@...hat.com>, linux-kernel@...r.kernel.org, kernel-team@...roid.com,
 linux-mm@...ck.org
Subject: Re: [PATCH 0/3] selftests/mm: revert pthread_barrier change and

On Fri, 18 Oct 2024 17:17:21 +0000 Edward Liaw <edliaw@...gle.com> wrote:

> Subject: [PATCH 0/3] selftests/mm: revert pthread_barrier change and

I simply removed the " and".

> Date: Fri, 18 Oct 2024 17:17:21 +0000
> X-Mailer: git-send-email 2.47.0.105.g07ac214952-goog
> 
> 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.
> 
> Edward Liaw (3):
>   Revert "selftests/mm: fix deadlock for fork after pthread_create on
>     ARM"
>   Revert "selftests/mm: replace atomic_bool with pthread_barrier_t"
>   selftests/mm: fix deadlock for fork after pthread_create with
>     atomic_bool

I added cc:stable to the first two patches as the thing-being-reverted
was cc:stable.