From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH] CRED: Move the exec mutex release out of bprm_free()
Date: Fri, 22 Aug 2008 09:32:15 +1000 (EST) [thread overview]
Message-ID: <alpine.LRH.1.10.0808220932010.17708@tundra.namei.org> (raw)
In-Reply-To: <20080821123907.4731.54839.stgit@warthog.procyon.org.uk>
On Thu, 21 Aug 2008, David Howells wrote:
> Move the exec mutex release out of free_bprm() and into the error handling
> paths of do_execve() and compat_do_execve(). install_exec_creds() already
> takes care of the success path.
>
> Signed-off-by: David Howells <dhowells@redhat.com>
This patch does not apply to my tree:
Applying CRED: Move the exec mutex release out of bprm_free()
error: patch failed: fs/compat.c:1373
error: fs/compat.c: patch does not apply
error: patch failed: fs/exec.c:1319
error: fs/exec.c: patch does not apply
Patch failed at 0001.
> ---
>
> fs/compat.c | 3 +--
> fs/exec.c | 7 ++-----
> 2 files changed, 3 insertions(+), 7 deletions(-)
>
>
> diff --git a/fs/compat.c b/fs/compat.c
> index 918f0f2..af24b8a 100644
> --- a/fs/compat.c
> +++ b/fs/compat.c
> @@ -1373,7 +1373,7 @@ int compat_do_execve(char * filename,
> file = open_exec(filename);
> retval = PTR_ERR(file);
> if (IS_ERR(file))
> - goto out_free;
> + goto out_unlock;
>
> sched_exec();
>
> @@ -1427,7 +1427,6 @@ out_file:
> allow_write_access(bprm->file);
> fput(bprm->file);
> }
> - goto out_free;
>
> out_unlock:
> mutex_unlock(¤t->cred_exec_mutex);
> diff --git a/fs/exec.c b/fs/exec.c
> index 7b71679..9fa9a2d 100644
> --- a/fs/exec.c
> +++ b/fs/exec.c
> @@ -1277,10 +1277,8 @@ EXPORT_SYMBOL(search_binary_handler);
> void free_bprm(struct linux_binprm *bprm)
> {
> free_arg_pages(bprm);
> - if (bprm->cred) {
> - mutex_unlock(¤t->cred_exec_mutex);
> + if (bprm->cred)
> abort_creds(bprm->cred);
> - }
> kfree(bprm);
> }
>
> @@ -1319,7 +1317,7 @@ int do_execve(char * filename,
> file = open_exec(filename);
> retval = PTR_ERR(file);
> if (IS_ERR(file))
> - goto out_free;
> + goto out_unlock;
>
> sched_exec();
>
> @@ -1376,7 +1374,6 @@ out_file:
> allow_write_access(bprm->file);
> fput(bprm->file);
> }
> - goto out_free;
>
> out_unlock:
> mutex_unlock(¤t->cred_exec_mutex);
>
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2008-08-21 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 12:39 David Howells
2008-08-21 23:32 ` James Morris [this message]
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=alpine.LRH.1.10.0808220932010.17708@tundra.namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.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
all inboxes | Powered by JetHome®