From: "Mickaël Salaün" <mic@digikod.net>
To: Jakub Kicinski <kuba@kernel.org>,
Kees Cook <keescook@chromium.org>,
Mark Brown <broonie@kernel.org>, Shuah Khan <shuah@kernel.org>,
davem@davemloft.net
Cc: "Mickaël Salaün" <mic@digikod.net>,
"Günther Noack" <gnoack@google.com>,
"Will Drewry" <wad@chromium.org>,
edumazet@google.com, jakub@cloudflare.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-security-module@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH v1 0/2] Merge TEST_F_FORK() into TEST_F()
Date: Tue, 5 Mar 2024 16:56:46 +0100 [thread overview]
Message-ID: <20240305155648.1292566-1-mic@digikod.net> (raw)
In-Reply-To: <20240305.eth2Ohcawa7u@digikod.net>
Hi,
This is a long due cleanup to merge TEST_F_FORK() into TEST_F().
This second version includes Jakub's "child" default value fix, proper
signal handling (TEST_SIGNAL), and move fixture setup and teardown to
the grandchild process by default.
This also removes the step counter and simplify Landlock's test
teardowns by removing some umount calls.
See https://lore.kernel.org/r/20240229005920.2407409-1-kuba@kernel.org
Regards,
Mickaël Salaün (2):
selftests/landlock: Redefine TEST_F() as TEST_F_FORK()
selftests/harness: Merge TEST_F_FORK() into TEST_F()
tools/testing/selftests/kselftest_harness.h | 72 ++++++++++-----------
tools/testing/selftests/landlock/common.h | 58 +----------------
tools/testing/selftests/landlock/fs_test.c | 22 +++----
3 files changed, 48 insertions(+), 104 deletions(-)
base-commit: 90d35da658da8cff0d4ecbb5113f5fac9d00eb72
--
2.44.0
next parent reply other threads:[~2024-03-05 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240305.eth2Ohcawa7u@digikod.net>
2024-03-05 15:56 ` Mickaël Salaün [this message]
2024-03-05 15:56 ` [PATCH v1 1/2] selftests/landlock: Redefine TEST_F() as TEST_F_FORK() Mickaël Salaün
2024-03-05 15:56 ` [PATCH v1 2/2] selftests/harness: Merge TEST_F_FORK() into TEST_F() Mickaël Salaün
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=20240305155648.1292566-1-mic@digikod.net \
--to=mic@digikod.net \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnoack@google.com \
--cc=jakub@cloudflare.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®