From: James Morris Subject: Re: [PATCH 0/4][RFC] NFSv3: implement extended attribute (XATTR) protocol Date: Fri, 9 Oct 2009 11:31:55 +1100 (EST) Message-ID: References: <20091008172123.GA24911@fieldses.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Sriram Ramkrishna , Trond Myklebust , linux-nfs@vger.kernel.org, Christoph Hellwig , Casey Schaufler , linux-fsdevel@vger.kernel.org To: "J. Bruce Fields" Return-path: In-Reply-To: <20091008172123.GA24911@fieldses.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, 8 Oct 2009, J. Bruce Fields wrote: > I assume that it was in order to avoid that question that this initial > implementation only exports the user.* namespace, since xattr's in that > name space are by design not given any special interpretation by the > filesystem--they just store and return opaque data. Correct -- there are no system semantics (beyond existing DACsecurity checks), so it's straightforward. Other namespaces would need to have semantics defined on a case by case basis. > > --b. > > > > > > > > > > > Note that I'll be giving a talk on this at LinuxCon on Thursday: > > > http://linuxcon.linuxfoundation.org/meetings/1589 So, in addition to > > > discussion here, please come along to the talk if you're at the conf, and > > > we may also be able to discuss it at Plumbers in one of the BoFs. > > > > > > > > > Ah, I was there, and I was asking around wanting to talk about the issue! > > Ah well. > > > > sri > -- James Morris