From: Andrew Morton <akpm@linux-foundation.org>
To: Edward Liaw <edliaw@google.com>
Cc: linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
Lokesh Gidra <lokeshgidra@google.com>,
Peter Xu <peterx@redhat.com>,
linux-kernel@vger.kernel.org, kernel-team@android.com,
linux-mm@kvack.org
Subject: Re: [PATCH 0/2] selftests/mm: fix deadlock after pthread_create
Date: Fri, 4 Oct 2024 16:54:52 -0700 [thread overview]
Message-ID: <20241004165452.a28856a9404a5a67d6fd201d@linux-foundation.org> (raw)
In-Reply-To: <20241003211716.371786-1-edliaw@google.com>
On Thu, 3 Oct 2024 21:17:09 +0000 Edward Liaw <edliaw@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?
prev parent reply other threads:[~2024-10-05 0:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 21:17 Edward Liaw
2024-10-03 21:17 ` [PATCH 1/2] selftests/mm: replace atomic_bool with pthread_barrier_t Edward Liaw
2024-10-06 17:53 ` Muhammad Usama Anjum
2024-10-18 14:37 ` Ryan Roberts
2024-10-18 17:17 ` Edward Liaw
2024-10-03 21:17 ` [PATCH 2/2] selftests/mm: fix deadlock for fork after pthread_create on ARM Edward Liaw
2024-10-04 23:54 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241004165452.a28856a9404a5a67d6fd201d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=edliaw@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lokeshgidra@google.com \
--cc=peterx@redhat.com \
--cc=shuah@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox