From: Chris Wright <chrisw@osdl.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, Chris Wright <chrisw@osdl.org>,
Stephen Smalley <sds@epoch.ncsc.mil>,
James Morris <jmorris@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] split bprm_apply_creds into two functions
Date: Tue, 4 Jan 2005 13:52:10 -0800 [thread overview]
Message-ID: <20050104135210.X2357@build.pdx.osdl.net> (raw)
In-Reply-To: <20050104183043.GA3592@IBM-BWN8ZTBWA01.austin.ibm.com>; from serue@us.ibm.com on Tue, Jan 04, 2005 at 12:30:43PM -0600
* Serge E. Hallyn (serue@us.ibm.com) wrote:
> The following patch splits bprm_apply_creds into two functions,
> bprm_apply_creds and bprm_post_apply_creds. The latter is called
> after the task_lock has been dropped. Without this patch, SELinux
> must drop the task_lock and re-acquire it during apply_creds, making
> the 'unsafe' flag meaningless to any later security modules. Please
> apply.
>
> Signed-off-by: Serge Hallyn <serue@us.ibm.com>
Signed-off-by: Chris Wright <chrisw@osdl.org>
next prev parent reply other threads:[~2005-01-04 21:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 18:30 Serge E. Hallyn
2005-01-04 21:41 ` Stephen Smalley
2005-01-04 21:52 ` Chris Wright [this message]
2005-01-05 14:43 ` [PATCH] [resend] " Serge E. Hallyn
2005-01-05 23:17 ` Chris Wright
2005-01-05 23:14 ` [PATCH] " Chris Wright
2005-01-05 23:16 ` Chris Wright
-- strict thread matches above, loose matches on Subject: below --
2004-12-15 20:00 [PATCH] Split " Serge E. Hallyn
2004-12-15 21:15 ` Stephen Smalley
2004-12-16 18:25 ` Serge E. Hallyn
2004-12-17 14:10 ` Stephen Smalley
2004-12-17 17:03 ` Chris Wright
2004-12-17 19:32 ` Serge E. Hallyn
2004-12-15 22:52 ` Chris Wright
2004-12-16 12:47 ` Stephen Smalley
2004-12-16 18:16 ` Serge E. Hallyn
2004-12-16 18:16 ` Stephen Smalley
2004-12-16 18:19 ` Chris Wright
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=20050104135210.X2357@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@epoch.ncsc.mil \
--cc=serue@us.ibm.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®