From: "Mickaël Salaün" <mic@digikod.net>
To: Shuah Khan <shuah@kernel.org>, Jakub Kicinski <kuba@kernel.org>,
Mark Brown <broonie@kernel.org>
Cc: "Christian Brauner" <brauner@kernel.org>,
"Kees Cook" <keescook@chromium.org>,
"Shengyu Li" <shengyu.li.evgeny@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
"Günther Noack" <gnoack@google.com>,
"Will Drewry" <wad@chromium.org>,
"kernel test robot" <oliver.sang@intel.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 0/9] Fix Kselftest's vfork() side effects
Date: Tue, 30 Apr 2024 15:54:38 +0200 [thread overview]
Message-ID: <20240430.eudae0Mahbie@digikod.net> (raw)
In-Reply-To: <20240429191911.2552580-1-mic@digikod.net>
Shuah, could you please take this series in your tree and push it to
next? This mainly fixes an issue in the pidfd tests and we should get
this merged before the final 6.9 release. Thanks.
Jakub, can you please review it?
Mark, it would be good to have your Tested-by tags. :)
On Mon, Apr 29, 2024 at 09:19:02PM +0200, Mickaël Salaün wrote:
> Hi,
>
> As reported by Kernel Test Robot [1], some pidfd tests fail. This is
> due to the use of vfork() which introduced some side effects.
> Similarly, while making it more generic, a previous commit made some
> Landlock file system tests flaky, and subject to the host's file system
> mount configuration.
>
> This series fixes all these side effects by replacing vfork() with
> clone3() and CLONE_VFORK, which is cleaner (no arbitrary shared memory)
> and makes the Kselftest framework more robust.
>
> I tried different approaches and I found this one to be the cleaner and
> less invasive for current test cases.
>
> This third series replace improve the clone3_vfork() helper and add
> Reviewed-by tags.
>
> I successfully ran the following tests (using TEST_F and
> fork/clone/clone3) with this series:
> - landlock:fs_test
> - landlock:net_test
> - landlock:ptrace_test
> - move_mount_set_group:move_mount_set_group_test
> - net/af_unix:scm_pidfd
> - perf_events:remove_on_exec
> - pidfd:pidfd_getfd_test
> - pidfd:pidfd_setns_test
> - seccomp:seccomp_bpf
> - user_events:abi_test
>
> [1] https://lore.kernel.org/oe-lkp/202403291015.1fcfa957-oliver.sang@intel.com
>
> Previous versions:
> v1: https://lore.kernel.org/r/20240426172252.1862930-1-mic@digikod.net
> v2: https://lore.kernel.org/r/20240429130931.2394118-1-mic@digikod.net
>
> Regards,
>
> Mickaël Salaün (9):
> selftests/pidfd: Fix config for pidfd_setns_test
> selftests/landlock: Fix FS tests when run on a private mount point
> selftests/harness: Fix fixture teardown
> selftests/harness: Fix interleaved scheduling leading to race
> conditions
> selftests/landlock: Do not allocate memory in fixture data
> selftests/harness: Constify fixture variants
> selftests/pidfd: Fix wrong expectation
> selftests/harness: Share _metadata between forked processes
> selftests/harness: Fix vfork() side effects
>
> tools/testing/selftests/kselftest_harness.h | 113 +++++++++++++-----
> tools/testing/selftests/landlock/fs_test.c | 83 ++++++++-----
> tools/testing/selftests/pidfd/config | 2 +
> .../selftests/pidfd/pidfd_setns_test.c | 2 +-
> 4 files changed, 135 insertions(+), 65 deletions(-)
>
>
> base-commit: e67572cd2204894179d89bd7b984072f19313b03
> --
> 2.44.0
>
next prev parent reply other threads:[~2024-04-30 13:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 19:19 [PATCH v3 0/9] Fix Kselftest's vfork() side effects Mickaël Salaün
2024-04-29 19:19 ` [PATCH v3 1/9] selftests/pidfd: Fix config for pidfd_setns_test Mickaël Salaün
2024-05-02 14:10 ` Christian Brauner
2024-04-29 19:19 ` [PATCH v3 2/9] selftests/landlock: Fix FS tests when run on a private mount point Mickaël Salaün
2024-04-29 19:19 ` [PATCH v3 3/9] selftests/harness: Fix fixture teardown Mickaël Salaün
2024-04-29 19:19 ` [PATCH v3 4/9] selftests/harness: Fix interleaved scheduling leading to race conditions Mickaël Salaün
2024-04-29 19:19 ` [PATCH v3 5/9] selftests/landlock: Do not allocate memory in fixture data Mickaël Salaün
2024-04-29 19:19 ` [PATCH v3 6/9] selftests/harness: Constify fixture variants Mickaël Salaün
2024-04-29 19:19 ` [PATCH v3 7/9] selftests/pidfd: Fix wrong expectation Mickaël Salaün
2024-05-02 14:12 ` Christian Brauner
2024-04-29 19:19 ` [PATCH v3 8/9] selftests/harness: Share _metadata between forked processes Mickaël Salaün
2024-04-29 19:19 ` [PATCH v3 9/9] selftests/harness: Fix vfork() side effects Mickaël Salaün
2024-04-30 13:54 ` Mickaël Salaün [this message]
2024-04-30 15:13 ` [PATCH v3 0/9] Fix Kselftest's " Jakub Kicinski
2024-04-30 16:38 ` Mickaël Salaün
2024-04-30 16:50 ` Kees Cook
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=20240430.eudae0Mahbie@digikod.net \
--to=mic@digikod.net \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=gnoack@google.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=shengyu.li.evgeny@gmail.com \
--cc=shuah@kernel.org \
--cc=wad@chromium.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