From: "Mickaël Salaün" <mic@digikod.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Mickaël Salaün" <mic@digikod.net>,
"Günther Noack" <gnoack@google.com>,
"Paul Moore" <paul@paul-moore.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: [GIT PULL] Landlock updates for v6.8
Date: Mon, 8 Jan 2024 12:33:11 +0100 [thread overview]
Message-ID: <20240108113311.192252-1-mic@digikod.net> (raw)
Hi Linus,
This PR adds new tests, a slight optimization, and some cosmetic changes.
Please pull these changes for v6.8-rc1. These 7 commits merged cleanly with
your master branch. The kernel code has been tested in the latest linux-next
releases for a few weeks. I rebased the latest patches with updated
descriptions though.
Test coverage for security/landlock is 92.4% of 710 lines according to
gcc/gcov-13, same as before because only semantic tests are added.
Regards,
Mickaël
--
The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mic/linux.git tags/landlock-6.8-rc1
for you to fetch changes up to 0daaa610c8e033cdfb420db728c2b40eb3a75134:
landlock: Optimize the number of calls to get_access_mask slightly (2024-01-03 12:43:17 +0100)
----------------------------------------------------------------
Landlock updates for v6.8-rc1
----------------------------------------------------------------
Günther Noack (5):
landlock: Remove remaining "inline" modifiers in .c files [v5.15]
landlock: Remove remaining "inline" modifiers in .c files [v6.1]
landlock: Remove remaining "inline" modifiers in .c files [v6.6]
selftests/landlock: Rename "permitted" to "allowed" in ftruncate tests
landlock: Optimize the number of calls to get_access_mask slightly
Mickaël Salaün (2):
selftests/landlock: Add tests to check unknown rule's access rights
selftests/landlock: Add tests to check unhandled rule's access rights
security/landlock/fs.c | 26 +++++-----
security/landlock/ruleset.c | 7 +--
tools/testing/selftests/landlock/fs_test.c | 80 +++++++++++++++++++++++++----
tools/testing/selftests/landlock/net_test.c | 59 ++++++++++++++++++++-
4 files changed, 145 insertions(+), 27 deletions(-)
next reply other threads:[~2024-01-08 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 11:33 Mickaël Salaün [this message]
2024-01-09 21:40 ` pr-tracker-bot
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=20240108113311.192252-1-mic@digikod.net \
--to=mic@digikod.net \
--cc=gnoack@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=torvalds@linux-foundation.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®