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" <gnoack3000@gmail.com>,
"Jeff Xu" <jeffxu@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.3
Date: Mon, 20 Feb 2023 19:47:22 +0100 [thread overview]
Message-ID: <20230220184722.573397-1-mic@digikod.net> (raw)
Hi Linus,
This PR improves documentation, and makes some tests more flexible to be
able to run on systems without overlayfs or with Yama restrictions.
Please pull this Landlock changes for v6.3-rc1 . These commits merged
cleanly with your tree, and have been successfully tested in the latest
linux-next releases for a few weeks.
Regards,
Mickaël
--
The following changes since commit b7bfaa761d760e72a969d116517eaa12e404c262:
Linux 6.2-rc3 (2023-01-08 11:49:43 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mic/linux.git tags/landlock-6.3-rc1
for you to fetch changes up to 1c1ea1c3e21d5ba0867f84f6ad04090bd477df25:
MAINTAINERS: Update Landlock repository (2023-02-10 09:41:55 +0100)
----------------------------------------------------------------
Landlock updates for v6.3-rc1
----------------------------------------------------------------
Jeff Xu (2):
selftests/landlock: Skip overlayfs tests when not supported
selftests/landlock: Test ptrace as much as possible with Yama
Mickaël Salaün (2):
landlock: Explain file descriptor access rights
MAINTAINERS: Update Landlock repository
Documentation/security/landlock.rst | 34 +++++++-
MAINTAINERS | 2 +-
tools/testing/selftests/landlock/fs_test.c | 47 ++++++++++
tools/testing/selftests/landlock/ptrace_test.c | 113 +++++++++++++++++++++----
4 files changed, 175 insertions(+), 21 deletions(-)
next reply other threads:[~2023-02-20 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 18:47 Mickaël Salaün [this message]
2023-02-22 20:58 ` 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=20230220184722.573397-1-mic@digikod.net \
--to=mic@digikod.net \
--cc=gnoack3000@gmail.com \
--cc=jeffxu@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®