From: "Mickaël Salaün" <mic@digikod.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Mickaël Salaün" <mic@digikod.net>,
"Daniel Burgener" <dburgener@linux.microsoft.com>,
"Günther Noack" <gnoack@google.com>,
"Matthieu Buffet" <matthieu@buffet.re>,
"Mikhail Ivanov" <ivanov.mikhail1@huawei-partners.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: [GIT PULL] Landlock fix for v6.12-rc7
Date: Sat, 9 Nov 2024 20:41:58 +0100 [thread overview]
Message-ID: <20241109194158.422529-1-mic@digikod.net> (raw)
Hi Linus,
This PR fixes issues in the Landlock's sandboxer sample and documentation,
slightly refactors helpers (required for ongoing patch series), and improve/fix
a feature merged in v6.12 (signal and abstract UNIX socket scoping).
Please pull these changes for v6.12-rc7 (or rc8, if any). These commits merge
cleanly with your master branch. The kernel code has been tested in the latest
linux-next releases for a few weeks, but I updated the last three patches with
cosmetic changes according to reviews.
Test coverage for security/landlock is 92.5% of 1129 lines according to
gcc/gcov-14, and it was 92.8% of 1134 lines before this PR.
Regards,
Mickaël
--
The following changes since commit 03197e40a22c2641a1f9d1744418cd29f4954b83:
landlock: Optimize scope enforcement (2024-11-09 19:52:13 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/mic/linux.git tags/landlock-6.12-rc7
for you to fetch changes up to 03197e40a22c2641a1f9d1744418cd29f4954b83:
landlock: Optimize scope enforcement (2024-11-09 19:52:13 +0100)
----------------------------------------------------------------
Landlock fix for v6.12-rc7
----------------------------------------------------------------
next reply other threads:[~2024-11-09 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 19:41 Mickaël Salaün [this message]
2024-11-09 21:59 ` [GIT PULL] Landlock fix for v6.12-rc7 Linus Torvalds
2024-11-10 18:56 ` Mickaël Salaün
2024-11-12 21:38 ` 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=20241109194158.422529-1-mic@digikod.net \
--to=mic@digikod.net \
--cc=dburgener@linux.microsoft.com \
--cc=gnoack@google.com \
--cc=ivanov.mikhail1@huawei-partners.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=matthieu@buffet.re \
--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