From: David Howells <dhowells@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dhowells@redhat.com, viro@ftp.linux.org.uk, sds@tycho.nsa.gov,
casey@schaufler-ca.com, linux-fsdevel@vger.kernel.org,
nfsv4@linux-nfs.org, linux-kernel@vger.kernel.org,
selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org
Subject: Re: Adding a security parameter to VFS functions
Date: Mon, 20 Aug 2007 13:09:52 +0100 [thread overview]
Message-ID: <11466.1187611792@redhat.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0708161550140.30176@woody.linux-foundation.org>
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> > Would you object greatly to functions like vfs_mkdir() gaining a security
> > parameter? What I'm thinking of is this:
> ...
> Why the *hell* would mkdir() be so magical as to need something like that?
If you look again, you'll notice that I said "functions like vfs_mkdir()". I
was I using vfs_mkdir() as an example. I didn't mean to apply this to
directory creation only. It would need to apply to all the vfs_*() entry
points called by nfsd and cachefiles.
David
prev parent reply other threads:[~2007-08-20 12:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 11:40 Adding a security parameter to VFS functions David Howells
2007-08-15 16:23 ` Casey Schaufler
2007-08-15 16:52 ` David Howells
2007-08-16 22:20 ` Andreas Gruenbacher
2007-08-16 22:36 ` Andreas Gruenbacher
2007-08-16 22:57 ` Linus Torvalds
2007-08-16 23:30 ` Kyle Moffett
2007-08-16 23:34 ` Al Viro
2007-08-17 18:05 ` Andreas Gruenbacher
2007-08-20 12:09 ` David Howells [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=11466.1187611792@redhat.com \
--to=dhowells@redhat.com \
--cc=casey@schaufler-ca.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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=torvalds@linux-foundation.org \
--cc=viro@ftp.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).