From: "Mickaël Salaün" <mic@digikod.net>
To: "Günther Noack" <gnoack@google.com>,
"Konstantin Meskhidze" <konstantin.meskhidze@huawei.com>
Cc: "Mickaël Salaün" <mic@digikod.net>,
"James Morris" <jmorris@namei.org>,
"Paul Moore" <paul@paul-moore.com>,
"Serge E . Hallyn" <serge@hallyn.com>,
linux-security-module@vger.kernel.org
Subject: [PATCH v1 0/2] Extend Landlock test to improve rule's coverage
Date: Mon, 20 Nov 2023 20:39:12 +0100 [thread overview]
Message-ID: <20231120193914.441117-1-mic@digikod.net> (raw)
Hi,
These are new tests to give more backward compatibility guarantees about
rule's access rights. This might be useful for changes happening in the
access right handling, especially with synthetic access rights:
https://lore.kernel.org/r/20231117154920.1706371-3-gnoack@google.com
Regards,
Mickaël Salaün (2):
selftests/landlock: Add tests to check undefined rule's access rights
selftests/landlock: Add tests to check unhandled rule's access rights
tools/testing/selftests/landlock/fs_test.c | 52 +++++++++++++++++++--
tools/testing/selftests/landlock/net_test.c | 50 +++++++++++++++++---
2 files changed, 90 insertions(+), 12 deletions(-)
base-commit: b85ea95d086471afb4ad062012a4d73cd328fa86
--
2.42.1
next reply other threads:[~2023-11-20 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 19:39 Mickaël Salaün [this message]
2023-11-20 19:39 ` [PATCH v1 1/2] selftests/landlock: Add tests to check undefined rule's access rights Mickaël Salaün
2023-11-24 17:07 ` Günther Noack
2023-11-30 9:17 ` Mickaël Salaün
2023-11-20 19:39 ` [PATCH v1 2/2] selftests/landlock: Add tests to check unhandled " Mickaël Salaün
2023-11-24 17:12 ` Günther Noack
2023-11-30 9:17 ` Mickaël Salaün
2023-11-27 8:04 ` Konstantin Meskhidze (A)
2023-11-30 9:18 ` 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=20231120193914.441117-1-mic@digikod.net \
--to=mic@digikod.net \
--cc=gnoack@google.com \
--cc=jmorris@namei.org \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
/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).