[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<171167227027.28813.3759046936061373590.git-patchwork-notify@kernel.org>
Date: Fri, 29 Mar 2024 00:31:10 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Edward Liaw <edliaw@...gle.com>
Cc: linux-kernel@...r.kernel.org, ast@...nel.org, daniel@...earbox.net,
john.fastabend@...il.com, andrii@...nel.org, martin.lau@...ux.dev,
eddyz87@...il.com, song@...nel.org, yonghong.song@...ux.dev,
kpsingh@...nel.org, sdf@...gle.com, haoluo@...gle.com, jolsa@...nel.org,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
akpm@...ux-foundation.org, shuah@...nel.org, nathan@...nel.org,
ndesaulniers@...gle.com, morbo@...gle.com, justinstitt@...gle.com,
jannh@...gle.com, linux-kselftest@...r.kernel.org, kernel-team@...roid.com,
lokeshgidra@...gle.com, bpf@...r.kernel.org, netdev@...r.kernel.org,
linux-mm@...ck.org, llvm@...ts.linux.dev
Subject: Re: [PATCH v3] selftests/mm: Fix ARM related issue with fork after
pthread_create
Hello:
This patch was applied to netdev/net.git (main)
by Andrew Morton <akpm@...ux-foundation.org>:
On Mon, 25 Mar 2024 19:40:52 +0000 you wrote:
> Following issue was observed while running the uffd-unit-tests selftest
> on ARM devices. On x86_64 no issues were detected:
>
> pthread_create followed by fork caused deadlock in certain cases
> wherein fork required some work to be completed by the created thread.
> Used synchronization to ensure that created thread's start function has
> started before invoking fork.
>
> [...]
Here is the summary with links:
- [v3] selftests/mm: Fix ARM related issue with fork after pthread_create
https://git.kernel.org/netdev/net/c/8c864371b2a1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists