From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Kees Cook" <kees@kernel•org>, "Mickaël Salaün" <mic@digikod•net>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the execve tree
Date: Thu, 19 Dec 2024 16:34:43 +1100 [thread overview]
Message-ID: <20241219163443.349fab59@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]
Hi all,
The following commits are also in the landlock tree as different commits
(but the same patches):
95b3cdafd7cb ("ima: instantiate the bprm_creds_for_exec() hook")
2a69962be4a7 ("samples/check-exec: Add an enlighten "inc" interpreter and 28 tests")
3e707b07f582 ("selftests: ktap_helpers: Fix uninitialized variable")
faf2d88e5567 ("samples/check-exec: Add set-exec")
0e7f90f34cf7 ("selftests/landlock: Add tests for execveat + AT_EXECVE_CHECK")
b083cc815376 ("selftests/exec: Add 32 tests for AT_EXECVE_CHECK and exec securebits")
a0623b2a1d59 ("security: Add EXEC_RESTRICT_FILE and EXEC_DENY_INTERACTIVE securebits")
a5874fde3c08 ("exec: Add a new AT_EXECVE_CHECK flag to execveat(2)")
These are commits
d294b3aee748 ("ima: instantiate the bprm_creds_for_exec() hook")
3cb0af26efa1 ("samples/check-exec: Add an enlighten "inc" interpreter and 28 tests")
027e1a676890 ("selftests: ktap_helpers: Fix uninitialized variable")
b8ef9d9f61cd ("samples/check-exec: Add set-exec")
297d25a26208 ("selftests/landlock: Add tests for execveat + AT_EXECVE_CHECK")
926b857736c8 ("selftests/exec: Add 32 tests for AT_EXECVE_CHECK and exec securebits")
4196eeb79f44 ("security: Add EXEC_RESTRICT_FILE and EXEC_DENY_INTERACTIVE securebits")
9f05363166c3 ("exec: Add a new AT_EXECVE_CHECK flag to execveat(2)")
from the landlock tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2024-12-19 5:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20241219163443.349fab59@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=kees@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mic@digikod$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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