From: "Mickaël Salaün" <mic@digikod.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Mickaël Salaün" <mic@digikod.net>,
"Christian Brauner" <brauner@kernel.org>,
"Tom Rix" <trix@redhat.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: [GIT PULL] Landlock fixes for v5.18
Date: Mon, 21 Mar 2022 12:59:13 +0100 [thread overview]
Message-ID: <20220321115913.478505-1-mic@digikod.net> (raw)
Hi Linus,
Please pull these Landlock updates for v5.18-rc1 . These two patches
have been successfully tested in the latest linux-next releases for
several weeks. They contain minor fixes:
* One addresses a memory leak in a user space sample. In practice, this
memory leak doesn't stay long because of the following execve call,
but let's fix it anyway.
* The second patch standardize the Landlock ruleset file descriptor name
with square brackets.
Regards,
Mickaël
--
The following changes since commit dcb85f85fa6f142aae1fe86f399d4503d49f2b60:
gcc-plugins/stackleak: Use noinstr in favor of notrace (2022-02-03 17:02:21 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mic/linux.git tags/landlock-5.18-rc1
for you to fetch changes up to aea0b9f2486da8497f35c7114b764bf55e17c7ea:
landlock: Use square brackets around "landlock-ruleset" (2022-02-04 14:07:44 +0100)
----------------------------------------------------------------
Landlock updates for v5.18-rc1
These two commits contain a minor fix for the sandboxer sample, and a
Landlock ruleset FD name standardization.
----------------------------------------------------------------
Christian Brauner (1):
landlock: Use square brackets around "landlock-ruleset"
Tom Rix (1):
samples/landlock: Fix path_list memory leak
samples/landlock/sandboxer.c | 1 +
security/landlock/syscalls.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
next reply other threads:[~2022-03-21 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 11:59 Mickaël Salaün [this message]
2022-03-21 17:37 ` Linus Torvalds
2022-03-23 9:45 ` Mickaël Salaün
2022-03-27 22:22 ` 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=20220321115913.478505-1-mic@digikod.net \
--to=mic@digikod.net \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=trix@redhat.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
all inboxes | Powered by JetHome®