From: "Fabio M. De Francesco" <fabio.maria.de.francesco@linux.intel.com>
To: Dorine Tipo <dorine.a.tipo@gmail.com>
Cc: mic@digikod.net, skhan@linuxfoundation.org,
outreachy@lists.linux.dev, Dorine Tipo <dorine.a.tipo@gmail.com>
Subject: Re: [PATCH 0/2] Add io_uring test with Landlock access control rules
Date: Tue, 26 Mar 2024 11:21:52 +0100 [thread overview]
Message-ID: <3631043.iIbC2pHGDl@fdefranc-mobl3> (raw)
In-Reply-To: <cover.1711331521.git.dorine.a.tipo@gmail.com>
On Monday, 25 March 2024 03:32:33 CET Dorine Tipo wrote:
> This patch series introduces a new test for verifying Landlock access
> control rules with io_uring operation, IORING_OP_OPENAT.
>
> The first patch (Add test for io_uring openat access control with
> Landlock rules) implements the actual test.
>
> - The test defines allowed and disallowed paths for access attempts.
> - It creates Landlock rulesets for both allowed and disallowed access.
> - It uses io_uring_prep_openat with the rulesets to attempt opening
> files. - The test verifies successful preparation for allowed access and
> expects submission failures for disallowed access.
>
> The second patch (Add liburing dependency for io_uring test) updates the
> Makefile to include the necessary liburing library.
Hi Dorine,
If I read your message correctly, patch 1/2 depends on 2/2 because
liburing is needed by tests in 1/2. Every single patch of a series must
build and link successfully. I think that patch 1/2 cannot link without
the changes that you put in patch 2/2. Am I missing something?
The prerequisites one must meet when sending series are that (1) that
series must be applicable to (based on) the most recent publicly available
official version of the subsystem/driver it is meant for, (2) for all n
patches of a series with N patches, patch n must not require any k > n
patch (i.e., k:=(n < k <= N)), and (3) each patch must always achieve a
logically self-contained objective.
Well, in theory you may think to reverse the order of the patches to meet
rule 2. But by doing so you would break rule 3 because the changes you
make in the Makefile would only be needed to build and link another patch so
they don't serve any self-contained purposes.
Therefore, please make a self-contained patch that includes all the
necessary changes to make it build and link.
Thanks,
Fabio
> This patch series improves Landlock's test coverage by incorporating
> io_uring operations and helps ensure Landlock effectively controls access
> through io_uring.
> It enhances the overall security posture of the system.
>
> The test has been successfully compiled using make run_tests -C landlock
> and successfully verifies Landlock access control with io_uring.
>
> Dorine Tipo (2):
> Add test for io_uring openat access control with Landlock rules
> Add liburing dependency for io_uring test
>
> tools/testing/selftests/landlock/Makefile | 4 +-
> tools/testing/selftests/landlock/fs_test.c | 132 +++++++++++++++++++++
> 2 files changed, 134 insertions(+), 2 deletions(-)
>
> --
> 2.25.1
prev parent reply other threads:[~2024-03-26 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 2:32 [PATCH 0/2] Add io_uring test with Landlock access control rules Dorine Tipo
2024-03-25 2:32 ` [PATCH 1/2] Add test for io_uring openat access control with Landlock rules Dorine Tipo
2024-03-25 2:32 ` [PATCH 2/2] Add liburing dependency for io_uring test Dorine Tipo
2024-03-26 10:21 ` Fabio M. De Francesco [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=3631043.iIbC2pHGDl@fdefranc-mobl3 \
--to=fabio.maria.de.francesco@linux.intel.com \
--cc=dorine.a.tipo@gmail.com \
--cc=mic@digikod.net \
--cc=outreachy@lists.linux.dev \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.