From: "J. Bruce Fields" <bfields@fieldses.org>
To: Erez Zadok <ezk-EX0cT3Az47bauI2f2gSDlQ@public.gmane.org>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>, nfs@lists.sourceforge.net
Subject: Re: [NFS] [PATCH] nfs4, special files, and set/listxattr asymmetry
Date: Tue, 8 Jan 2008 16:57:37 -0500 [thread overview]
Message-ID: <20080108215736.GP22155@fieldses.org> (raw)
In-Reply-To: <200801082147.m08LlF3D023364-zop+azHP2WsZjdeEBZXbMidm6ipF23ct@public.gmane.org>
On Tue, Jan 08, 2008 at 04:47:15PM -0500, Erez Zadok wrote:
> A few months ago I looked into the issue of xattrs and copyup in more
> detail, when I was tracking a problem for a user using an SE-linux enabled
> livecd with unionfs. I didn't realize before then that selinux made such a
> heavy use of xattrs. After tracking down the code maze I found out that the
> list of xattrs being defined/used depends on your overall security mode and
> global security ops.
>
> Anyway, xattrs can be used for security reasons, and really any semantics
> could be attached to them. So in Unionfs I take the conservative approach:
> if unionfs is compiled with xattr support, then during copyup I try to copy
> the xattrs too (if any exist). If unionfs fails to copyup the xattrs, then
> I abort the copyup. I figured it's safer to abort the copyup (which is
> typically initiated when trying to modify a file on a readonly
> branch/media), than to potentially open up a security hole by giving a
> copied-up file more permissions than its source file may have had. This
> policy has so far worked for unionfs, at least for those users who use
> xattrs/selinux, and in my limited testing. But maybe I've got to rethink
> it?
>
> NFS in some sense shares some common traits with a stackable file system, in
> that it has three "layers": client -> server -> backing-store f/s. I'm
> curious how does nfs/d handle xattrs (and selinux's use of them)? Does the
> client depend on having xattr support of any sort? Does the server depend
> on having xattr support in the export f/s? How do you handle mixes of those
> when one of the three layers has xattr support and another doesn't?
We ignore xattr's entirely for now. The labeled nfs people (mailing
list at labeled-nfs@linux-nfs.org) have plans to address the selinux
case, but I haven't really followed that.
--b.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2008-01-08 21:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 3:14 [NFS] [PATCH] nfs4, special files, and set/listxattr asymmetry Erez Zadok
[not found] ` <200801080314.m083EVbb011378-zop+azHP2WsZjdeEBZXbMidm6ipF23ct@public.gmane.org>
2008-01-08 3:34 ` Trond Myklebust
[not found] ` <1199763245.21371.6.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-01-08 17:46 ` J. Bruce Fields
2008-01-08 21:26 ` Erez Zadok
[not found] ` <200801082126.m08LQTZm021972-zop+azHP2WsZjdeEBZXbMidm6ipF23ct@public.gmane.org>
2008-01-08 21:45 ` J. Bruce Fields
2008-01-08 21:48 ` Erez Zadok
2008-01-15 21:43 ` [NFS] [PATCH] nfs4: allow nfsv4 acls on non-regular-files J. Bruce Fields
2008-01-15 21:48 ` Trond Myklebust
2008-01-08 18:20 ` [NFS] [PATCH] nfs4, special files, and set/listxattr asymmetry J. Bruce Fields
2008-01-08 21:47 ` Erez Zadok
[not found] ` <200801082147.m08LlF3D023364-zop+azHP2WsZjdeEBZXbMidm6ipF23ct@public.gmane.org>
2008-01-08 21:57 ` J. Bruce Fields [this message]
2008-01-08 22:05 ` Dave Quigley
[not found] ` <1199829935.8434.75.camel-88+Bj4OksMGWPftkNcioYDMZycKHmlmlfvIqQ387n9k@public.gmane.org>
2008-01-08 22:25 ` J. Bruce Fields
2008-01-08 22:18 ` Dave Quigley
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=20080108215736.GP22155@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=ezk-EX0cT3Az47bauI2f2gSDlQ@public.gmane.org \
--cc=nfs@lists.sourceforge.net \
/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.