From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Eric Biederman <ebiederm@xmission.com>,
Kees Cook <keescook@chromium.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>
Cc: linux-security-module <linux-security-module@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] fs/exec: remove current->in_execve flag
Date: Sun, 28 Jan 2024 23:16:09 +0900 [thread overview]
Message-ID: <e938c37b-d615-4be4-a2da-02b904b7072f@I-love.SAKURA.ne.jp> (raw)
This is a follow up series for removing current->in_execve flag.
https://lkml.kernel.org/r/b5a12ecd-468d-4b50-9f8c-17ae2a2560b4@I-love.SAKURA.ne.jp
[PATCH 1/3] LSM: add security_bprm_aborting_creds() hook
[PATCH 2/3] tomoyo: replace current->in_execve flag with security_bprm_aborting_creds() hook
[PATCH 3/3] fs/exec: remove current->in_execve flag
fs/exec.c | 4 +---
include/linux/lsm_hook_defs.h | 1 +
include/linux/sched.h | 3 ---
include/linux/security.h | 5 +++++
security/security.c | 14 ++++++++++++++
security/tomoyo/tomoyo.c | 22 ++++++----------------
6 files changed, 27 insertions(+), 22 deletions(-)
(Please apply directly to linux.git tree if this series is OK, for
currently TOMOYO's tree is unavailable.)
next reply other threads:[~2024-01-28 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 14:16 Tetsuo Handa [this message]
2024-01-28 14:16 ` [PATCH 1/3] LSM: add security_bprm_aborting_creds() hook Tetsuo Handa
2024-01-29 4:10 ` Eric W. Biederman
2024-01-29 4:46 ` Tetsuo Handa
2024-01-29 18:15 ` Eric W. Biederman
2024-01-30 10:42 ` Tetsuo Handa
2024-01-28 14:17 ` [PATCH 2/3] tomoyo: replace current->in_execve flag with " Tetsuo Handa
2024-01-28 14:17 ` [PATCH 3/3] fs/exec: remove current->in_execve flag Tetsuo Handa
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=e938c37b-d615-4be4-a2da-02b904b7072f@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=jack@suse.cz \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).