From: Jeff Mahoney <jeffm@suse.com>
To: Jeffrey Mahoney <jeffm@suse.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Smalley <sds@epoch.ncsc.mil>,
Chris Wright <chrisw@osdl.org>
Subject: Re: [PATCH 1/4] vfs: adds the S_PRIVATE flag and adds use to security
Date: Thu, 03 Mar 2005 20:47:10 -0500 [thread overview]
Message-ID: <4227BE1E.7070601@suse.com> (raw)
In-Reply-To: <20050301153717.GB18215@locomotive.unixthugs.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeffrey Mahoney wrote:
> This patch adds an S_PRIVATE flag to inode->i_flags to mark an inode as
> filesystem-internal. As such, it should be excepted from the security
> infrastructure to allow the filesystem to perform its own access control.
> @@ -1459,12 +1469,16 @@ static inline void security_inode_post_l
> struct inode *dir,
> struct dentry *new_dentry)
> {
> + if (unlikely (IS_PRIVATE (new_dentry->d_inode)))
> + return;
> security_ops->inode_post_link (old_dentry, dir, new_dentry);
> }
>
Internal testing has shown that this operation will cause an Oops on
NFS. The assumption that a link operation will return an instantiated
dentry is invalid, and thus new_dentry->d_inode will be NULL on NFS
filesystems. I'll send out a revised version later this evening.
- -Jeff
- --
Jeff Mahoney
SuSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFCJ74eLPWxlyuTD7IRAg3zAJ4w5ThhGVHoTNKf+4TyqwU/NtRUvACfWnje
EIiFuTZPWZq245g/9xrkZLA=
=hTpo
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-03-04 2:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 15:37 [PATCH 1/4] vfs: adds the S_PRIVATE flag and adds use to security Jeffrey Mahoney
2005-03-04 1:47 ` Jeff Mahoney [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-04 19:52 Jeffrey Mahoney
2005-03-05 5:28 ` Andrew Morton
2005-03-05 17:42 ` Jeff Mahoney
2005-03-07 14:53 ` Stephen Smalley
2005-03-08 3:43 ` Chris Wright
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=4227BE1E.7070601@suse.com \
--to=jeffm@suse.com \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@epoch.ncsc.mil \
--cc=torvalds@osdl.org \
/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.