From: James Morris <jmorris@namei.org>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: lsm <linux-security-module@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@sous-sol.org>,
Eric Paris <eparis@parisplace.org>,
Casey Schaufler <casey@schaufler-ca.com>,
"Serge E. Hallyn" <serue@us.ibm.com>
Subject: Re: [PATCH] security: split proc ptrace checking into read vs. attach
Date: Tue, 20 May 2008 10:37:26 +1000 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0805201035550.8661@us.intercode.com.au> (raw)
In-Reply-To: <1211200369.7486.38.camel@moss-spartans.epoch.ncsc.mil>
On Mon, 19 May 2008, Stephen Smalley wrote:
> No change in the patch since the prior RFC. I think this is ready for the
> for-akpm branch of selinux, targeting 2.6.27.
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/selinux-2.6.git#for-akpm
- James
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2008-05-20 0:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 12:32 Stephen Smalley
2008-05-19 22:42 ` Chris Wright
2008-05-20 0:37 ` 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=Xine.LNX.4.64.0805201035550.8661@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=chrisw@sous-sol.org \
--cc=eparis@parisplace.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--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
Powered by JetHome