LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Kentaro Takeda <takedakn@nttdata.co.jp> To: Andrew Morton <akpm@linux-foundation.org> Cc: Toshiharu Harada <haradats@nttdata.co.jp>, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>, David Howells <dhowells@redhat.com> Subject: [TOMOYO #12 (2.6.28-rc2-mm1) 02/11] Add in_execve flag into task_struct. Date: Tue, 04 Nov 2008 15:08:49 +0900 [thread overview] Message-ID: <20081104060936.021370709@nttdata.co.jp> (raw) In-Reply-To: 20081104060847.086543472@nttdata.co.jp This patch allows LSM modules to determine whether current process is in an execve operation or not so that they can behave differently while an execve operation is in progress. This allows TOMOYO to dispense with a readability check on a file to be executed under the process's current credentials, and to do it instead under the proposed credentials. This is required with the new COW credentials because TOMOYO is no longer allowed to mark the state temporarily in the security struct attached to the task_struct. Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> Signed-off-by: David Howells <dhowells@redhat.com> --- fs/compat.c | 3 +++ fs/exec.c | 3 +++ include/linux/sched.h | 2 ++ 3 files changed, 8 insertions(+) --- linux-2.6.28-rc2-mm1.orig/fs/compat.c +++ linux-2.6.28-rc2-mm1/fs/compat.c @@ -1396,6 +1396,7 @@ int compat_do_execve(char * filename, retval = mutex_lock_interruptible(¤t->cred_exec_mutex); if (retval < 0) goto out_free; + current->in_execve = 1; retval = -ENOMEM; bprm->cred = prepare_exec_creds(); @@ -1448,6 +1449,7 @@ int compat_do_execve(char * filename, goto out; /* execve succeeded */ + current->in_execve = 0; mutex_unlock(¤t->cred_exec_mutex); acct_update_integrals(current); free_bprm(bprm); @@ -1464,6 +1466,7 @@ out_file: } out_unlock: + current->in_execve = 0; mutex_unlock(¤t->cred_exec_mutex); out_free: --- linux-2.6.28-rc2-mm1.orig/fs/exec.c +++ linux-2.6.28-rc2-mm1/fs/exec.c @@ -1301,6 +1301,7 @@ int do_execve(char * filename, retval = mutex_lock_interruptible(¤t->cred_exec_mutex); if (retval < 0) goto out_free; + current->in_execve = 1; retval = -ENOMEM; bprm->cred = prepare_exec_creds(); @@ -1354,6 +1355,7 @@ int do_execve(char * filename, goto out; /* execve succeeded */ + current->in_execve = 0; mutex_unlock(¤t->cred_exec_mutex); acct_update_integrals(current); free_bprm(bprm); @@ -1372,6 +1374,7 @@ out_file: } out_unlock: + current->in_execve = 0; mutex_unlock(¤t->cred_exec_mutex); out_free: --- linux-2.6.28-rc2-mm1.orig/include/linux/sched.h +++ linux-2.6.28-rc2-mm1/include/linux/sched.h @@ -1095,6 +1095,8 @@ struct task_struct { /* ??? */ unsigned int personality; unsigned did_exec:1; + unsigned in_execve:1; /* Tell the LSMs that the process is doing an + * execve */ pid_t pid; pid_t tgid; --
next prev parent reply other threads:[~2008-11-04 6:11 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-04 6:08 [TOMOYO #12 (2.6.28-rc2-mm1) 00/11] TOMOYO Linux Kentaro Takeda 2008-11-04 6:08 ` [TOMOYO #12 (2.6.28-rc2-mm1) 01/11] Introduce security_path_clear() hook Kentaro Takeda 2008-11-04 6:08 ` Kentaro Takeda [this message] 2008-11-05 23:12 ` [TOMOYO #12 (2.6.28-rc2-mm1) 02/11] Add in_execve flag into task_struct Andrew Morton 2008-11-04 6:08 ` [TOMOYO #12 (2.6.28-rc2-mm1) 03/11] Singly linked list implementation Kentaro Takeda 2008-11-05 23:12 ` Andrew Morton 2008-11-04 6:08 ` [TOMOYO #12 (2.6.28-rc2-mm1) 04/11] Introduce d_realpath() Kentaro Takeda 2008-11-05 23:12 ` Andrew Morton 2008-11-17 6:52 ` Kentaro Takeda 2008-11-04 6:08 ` [TOMOYO #12 (2.6.28-rc2-mm1) 05/11] Memory and pathname management functions Kentaro Takeda 2008-11-05 23:12 ` Andrew Morton 2008-11-10 10:34 ` Kentaro Takeda 2008-11-11 5:04 ` Andrew Morton 2008-11-11 6:34 ` Kentaro Takeda 2008-11-11 6:46 ` Andrew Morton 2008-11-11 7:32 ` Kentaro Takeda 2008-11-04 6:08 ` [TOMOYO #12 (2.6.28-rc2-mm1) 06/11] Common functions for TOMOYO Linux Kentaro Takeda 2008-11-05 23:12 ` Andrew Morton 2008-11-06 21:46 ` [TOMOYO #12 (2.6.28-rc2-mm1) 06/11] Common functions for TOMOYOLinux Tetsuo Handa 2008-11-08 16:38 ` Tetsuo Handa 2008-11-10 0:41 ` Serge E. Hallyn 2008-11-10 2:24 ` Tetsuo Handa 2008-11-10 2:52 ` Serge E. Hallyn 2008-11-10 3:30 ` Tetsuo Handa 2008-11-10 14:00 ` Serge E. Hallyn 2008-11-10 10:35 ` [TOMOYO #12 (2.6.28-rc2-mm1) 06/11] Common functions for TOMOYO Linux Kentaro Takeda 2008-11-14 9:22 ` Kentaro Takeda 2008-11-04 6:08 ` [TOMOYO #12 (2.6.28-rc2-mm1) 07/11] File operation restriction part Kentaro Takeda 2008-11-04 6:08 ` [TOMOYO #12 (2.6.28-rc2-mm1) 08/11] Domain transition handler Kentaro Takeda 2008-11-04 6:08 ` [TOMOYO #12 (2.6.28-rc2-mm1) 09/11] LSM adapter functions Kentaro Takeda 2008-11-04 6:08 ` [TOMOYO #12 (2.6.28-rc2-mm1) 10/11] Kconfig and Makefile Kentaro Takeda 2008-11-04 6:08 ` [TOMOYO #12 (2.6.28-rc2-mm1) 11/11] MAINTAINERS info Kentaro Takeda
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=20081104060936.021370709@nttdata.co.jp \ --to=takedakn@nttdata.co.jp \ --cc=akpm@linux-foundation.org \ --cc=dhowells@redhat.com \ --cc=haradats@nttdata.co.jp \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-security-module@vger.kernel.org \ --cc=penguin-kernel@I-love.SAKURA.ne.jp \ /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: linkBe 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 NNTP newsgroup(s).