From: Jeff Xu <jeffxu@google.com>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: jeffxu@chromium.org, jorgelo@chromium.org, keescook@chromium.org,
linux-security-module@vger.kernel.org, groeck@chromium.org,
gnoack@google.com
Subject: Re: [PATCH v8 0/1] selftests/landlock: fix fs_tests when overlayfs
Date: Fri, 13 Jan 2023 18:17:37 -0800 [thread overview]
Message-ID: <CALmYWFsmKn9-OJ5a+OYjXcWn_XoULhL3efgTEfOFRXXZOf5UFQ@mail.gmail.com> (raw)
In-Reply-To: <ab279390-84e1-0bcc-29ca-eea673fdd14c@digikod.net>
Awesome, thanks!
On Fri, Jan 13, 2023 at 11:58 AM Mickaël Salaün <mic@digikod.net> wrote:
>
> Thanks Jeff! I pushed this patch in -next:
> https://git.kernel.org/pub/scm/linux/kernel/git/mic/linux.git/log/?h=next
>
>
> On 13/01/2023 06:32, jeffxu@chromium.org wrote:
> > From: Jeff Xu <jeffxu@google.com>
> >
> > Overlayfs can be disabled in kernel config, causing related tests to
> > fail. Adding a check for overlayfs’s supportability at runtime,
> > so we can call SKIP() when needed.
> >
> > Note:
> > Below comments are raised during V7 discussion:
> >
> > Currently SKIP() is applied to FIXTURE_SETUP, FIXTURE_TEARDOWN,
> > TEST_F_FORK, this is because SKIP() apply within the function
> > scope, not the testcase.
> >
> > We would like test infra to have a dedicated environment
> > check hook (FIXTURE_ENV_CHECK) in test infra, called before
> > FIXTURE_SETUP(). If the environment check fails, the remaining
> > of the test will be skipped. The benefit of these are two:
> > 1> if env check pass, in theory, the test should pass.
> > 2> if env check fail, no need to call setup, so no need to cleanup
> > resource.
> >
> > v8:
> > style change, no logic change.
> >
> > v7:
> > https://lore.kernel.org/all/20221229211446.3154454-1-jeffxu@google.com/
> > Fix bug in supports_overlayfs().
> > Manual test with kernel with and without overlayfs.
> >
> > v6: https://lore.kernel.org/all/20221229201215.3006512-1-jeffxu@google.com/
> > In v4, the SKIP() was applied at FIXTURE_SETUP() after mount() fail,
> > however, FIXTURE_TEARDOWN() will fail. It might be complicated
> > for test infra or testcase itself to have cleanup code handing the
> > success/failure of steps in SETUP().
> >
> > This patch changes the approach, it calls supports_overlay() and SKIP()
> > at the beginning of FIXTURE_SETUP(), FIX_TEARDOWN(), TEST_F_FORK().
> > Because no modification of system is done by the test, cleanup is not
> > needed.
> >
> > v4:
> > https://lore.kernel.org/all/20220823010216.2653012-1-jeffxu@google.com/
> >
> >
> > Jeff Xu (1):
> > selftests/landlock: skip overlayfs test when not support
> >
> > tools/testing/selftests/landlock/fs_test.c | 48 ++++++++++++++++++++++
> > 1 file changed, 48 insertions(+)
> >
> >
> > base-commit: 963a70bee5880640d0fd83ed29dc1e7ec0d2bd4a
prev parent reply other threads:[~2023-01-14 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 5:32 [PATCH v8 0/1] selftests/landlock: fix fs_tests when overlayfs jeffxu
2023-01-13 5:32 ` [PATCH v8 1/1] selftests/landlock: skip overlayfs test when not support jeffxu
2023-01-13 19:58 ` [PATCH v8 0/1] selftests/landlock: fix fs_tests when overlayfs Mickaël Salaün
2023-01-14 2:17 ` Jeff Xu [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=CALmYWFsmKn9-OJ5a+OYjXcWn_XoULhL3efgTEfOFRXXZOf5UFQ@mail.gmail.com \
--to=jeffxu@google.com \
--cc=gnoack@google.com \
--cc=groeck@chromium.org \
--cc=jeffxu@chromium.org \
--cc=jorgelo@chromium.org \
--cc=keescook@chromium.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
/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;
as well as URLs for NNTP newsgroup(s).