mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
	Andrew Morton <akpm@osdl.org>, Chris Wright <chrisw@osdl.org>,
	James Morris <jmorris@redhat.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Split bprm_apply_creds into two functions
Date: Fri, 17 Dec 2004 09:03:18 -0800	[thread overview]
Message-ID: <20041217090317.V2357@build.pdx.osdl.net> (raw)
In-Reply-To: <1103292602.3437.40.camel@moss-spartans.epoch.ncsc.mil>; from sds@epoch.ncsc.mil on Fri, Dec 17, 2004 at 09:10:02AM -0500

* Stephen Smalley (sds@epoch.ncsc.mil) wrote:
> On Thu, 2004-12-16 at 13:25, Serge E. Hallyn wrote:
> > Thanks.  Here is an updated patch.
> > 
> > -serge
> > 
> > Signed-off-by: Serge Hallyn <serue@us.ibm.com>
> 
> Ok with me.  Chris, would it help alleviate your concerns to give the
> hook a clearer name and description, e.g. bprm_post_apply_creds and move
> the discussion about performing other state changes on the process like
> closing descriptors from the current description of bprm_apply_creds to
> it?

Yes.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  reply	other threads:[~2004-12-17 17:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-15 20:00 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 [this message]
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
2005-01-04 18:30 [PATCH] split " Serge E. Hallyn
2005-01-04 21:41 ` Stephen Smalley
2005-01-04 21:52 ` Chris Wright
2005-01-05 23:14 ` Chris Wright
2005-01-05 23:16   ` 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=20041217090317.V2357@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®