From: James Morris <jmorris@namei.org>
To: Christoph Hellwig <hch@lst.de>
Cc: nfsv4@linux-nfs.org, Chris Wright <chrisw@sous-sol.org>,
linux-fsdevel@vger.kernel.org,
linux-security-module@vger.kernel.org, viro@zeniv.linux.org.uk,
selinux@tycho.nsa.gov, Casey Schaufler <casey@schaufler-ca.com>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [PATCH]Introduce generalized hooks for getting and setting inode secctx.
Date: Tue, 29 Apr 2008 01:04:41 +1000 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0804290104000.2081@us.intercode.com.au> (raw)
In-Reply-To: <20080428060620.GA9902@lst.de>
On Mon, 28 Apr 2008, Christoph Hellwig wrote:
> On Mon, Apr 28, 2008 at 09:33:22AM +1000, James Morris wrote:
> > Cristoph, Casey -- any chance of getting ack or nack on this before the
> > merge window closes?
>
> No concernes about this patch, but as usual strong objections against
> introducing it without the actual user.
Ok, we might put them into a labeled-nfs tree rather than pushing them to
mainline at this stage.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2008-04-28 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 16:57 [PATCH]Introduce generalized hooks for getting and setting inode secctx David P. Quigley
[not found] ` <1208969836-8129-1-git-send-email-dpquigl-+05T5uksL2qpZYMLLGbcSA@public.gmane.org>
2008-04-23 16:57 ` [PATCH 1/2] VFS: Factor out part of vfs_setxattr so it can be called from the SELinux hook for inode_setsecctx David P. Quigley
2008-04-23 16:57 ` [PATCH 2/2] LSM/SELinux: inode_{get,set,notify}secctx hooks to access LSM security context information David P. Quigley
2008-04-27 23:33 ` [PATCH]Introduce generalized hooks for getting and setting inode secctx James Morris
2008-04-28 6:06 ` Christoph Hellwig
2008-04-28 15:04 ` James Morris [this message]
2008-04-28 15:10 ` Dave Quigley
2008-04-28 15:02 ` Casey Schaufler
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.0804290104000.2081@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=chrisw@sous-sol.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).