[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<170978643095.7855.10065526694998979631.git-patchwork-notify@kernel.org>
Date: Thu, 07 Mar 2024 04:40:30 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Mickaël Salaün <mic@...ikod.net>@codeaurora.org
Cc: davem@...emloft.net, kuba@...nel.org, keescook@...omium.org,
broonie@...nel.org, shuah@...nel.org, gnoack@...gle.com, wad@...omium.org,
edumazet@...gle.com, jakub@...udflare.com, pabeni@...hat.com,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-security-module@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] selftests/harness: Fix TEST_F()'s vfork handling
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 5 Mar 2024 21:10:29 +0100 you wrote:
> Always run fixture setup in the grandchild process, and by default also
> run the teardown in the same process. However, this change makes it
> possible to run the teardown in a parent process when
> _metadata->teardown_parent is set to true (e.g. in fixture setup).
>
> Fix TEST_SIGNAL() by forwarding grandchild's signal to its parent. Fix
> seccomp tests by running the test setup in the parent of the test
> thread, as expected by the related test code. Fix Landlock tests by
> waiting for the grandchild before processing _metadata.
>
> [...]
Here is the summary with links:
- selftests/harness: Fix TEST_F()'s vfork handling
https://git.kernel.org/netdev/net-next/c/41cca0542d7c
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