From: Greg KH <gregkh@suse.de>
To: James Morris <jmorris@namei.org>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
"David P. Quigley" <dpquigl@tycho.nsa.gov>,
casey@schaufler-ca.com, ebiederm@xmission.com,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH 3/3] sysfs: Add labeling support for sysfs
Date: Wed, 9 Sep 2009 20:01:21 -0700 [thread overview]
Message-ID: <20090910030121.GA32239@suse.de> (raw)
In-Reply-To: <alpine.LRH.2.00.0909101040460.30636@tundra.namei.org>
On Thu, Sep 10, 2009 at 10:40:59AM +1000, James Morris wrote:
> Thanks, all applied to
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6#next
Um, wait, what about the sysfs maintainer's review? :)
I also want to see Casey agree with this as well.
thanks,
greg k-h
next prev parent reply other threads:[~2009-09-10 3:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 18:25 [PATCH] Security/sysfs: Enable security xattrs to be set on sysfs files, directories, and symlinks David P. Quigley
2009-09-03 18:25 ` [PATCH 1/3] VFS: Factor out part of vfs_setxattr so it can be called from the SELinux hook for inode_setsecctx David P. Quigley
2009-09-04 15:31 ` Serge E. Hallyn
2009-09-03 18:25 ` [PATCH 2/3] LSM/SELinux: inode_{get,set,notify}secctx hooks to access LSM security context information David P. Quigley
2009-09-04 15:49 ` Serge E. Hallyn
2009-09-04 16:21 ` Stephen Smalley
2009-09-03 18:25 ` [PATCH 3/3] sysfs: Add labeling support for sysfs David P. Quigley
2009-09-04 16:03 ` Serge E. Hallyn
2009-09-07 1:48 ` James Morris
2009-09-09 18:25 ` Stephen Smalley
2009-09-10 0:40 ` James Morris
2009-09-10 3:01 ` Greg KH [this message]
2009-09-10 3:48 ` Casey Schaufler
2009-09-10 12:14 ` Stephen Smalley
2009-09-10 10:31 ` James Morris
2009-09-11 4:17 ` Casey Schaufler
2009-09-11 4:25 ` Greg KH
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=20090910030121.GA32239@suse.de \
--to=gregkh@suse.de \
--cc=casey@schaufler-ca.com \
--cc=dpquigl@tycho.nsa.gov \
--cc=ebiederm@xmission.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
/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