From: Christoph Hellwig <hch@lst.de>
To: James Morris <jmorris@namei.org>
Cc: "David P. Quigley" <dpquigl@tycho.nsa.gov>,
Casey Schaufler <casey@schaufler-ca.com>,
Chris Wright <chrisw@sous-sol.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
hch@lst.de, viro@zeniv.linux.org.uk, selinux@tycho.nsa.gov,
linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, nfsv4@linux-nfs.org
Subject: Re: [PATCH]Introduce generalized hooks for getting and setting inode secctx.
Date: Mon, 28 Apr 2008 08:06:20 +0200 [thread overview]
Message-ID: <20080428060620.GA9902@lst.de> (raw)
In-Reply-To: <Xine.LNX.4.64.0804280932520.17090@us.intercode.com.au>
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.
next prev parent reply other threads:[~2008-04-28 6:06 UTC|newest]
Thread overview: 15+ 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
2008-04-23 16:57 ` David P. Quigley
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 ` 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-23 16:57 ` David P. Quigley
2008-04-27 23:33 ` [PATCH]Introduce generalized hooks for getting and setting inode secctx James Morris
2008-04-27 23:33 ` James Morris
2008-04-28 6:06 ` Christoph Hellwig [this message]
2008-04-28 15:04 ` James Morris
2008-04-28 15:04 ` James Morris
2008-04-28 15:10 ` Dave Quigley
2008-04-28 15:10 ` Dave Quigley
2008-04-28 15:02 ` Casey Schaufler
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=20080428060620.GA9902@lst.de \
--to=hch@lst.de \
--cc=casey@schaufler-ca.com \
--cc=chrisw@sous-sol.org \
--cc=dpquigl@tycho.nsa.gov \
--cc=jmorris@namei.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.