Return-Path: linux-nfs-owner@vger.kernel.org Received: from e8.ny.us.ibm.com ([32.97.182.138]:39174 "EHLO e8.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752822Ab3JZRrG (ORCPT ); Sat, 26 Oct 2013 13:47:06 -0400 Received: from /spool/local by e8.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Sat, 26 Oct 2013 13:47:05 -0400 In-Reply-To: References: <1382560643.6924.12.camel@heisenberg.scientia.net> <1382624000.6907.8.camel@heisenberg.scientia.net> <1382630468.6907.58.camel@heisenberg.scientia.net> <625CAA34-BD6C-4283-86D0-3F8B460D54D0@netapp.com> <1382635350.6907.83.camel@heisenberg.scientia.net> <20131025140846.GB20497@fieldses.org> <526A8D9A.8090008@gmail.com> <7C1323EE-D63F-4F93-A44D-E7DDB0C61BF0@netapp.com> To: "Myklebust, Trond" Cc: Dr Fields James Bruce , Christoph Anton Mitterer , Mailing List Linux NFS , linux-nfs-owner@vger.kernel.org, Wheeler Ric MIME-Version: 1.0 Subject: Re: XATTRs in NFS? From: Marc Eshel Message-ID: Date: Sat, 26 Oct 2013 10:46:59 -0700 Content-Type: text/plain; charset="US-ASCII" Sender: linux-nfs-owner@vger.kernel.org List-ID: linux-nfs-owner@vger.kernel.org wrote on 10/26/2013 06:20:12 AM: > I'd rather look bad for not supporting a broken filesystem feature > than have to deal with the abiove mentioned side-effects. Until the > xattr interface is properly documented and standardised so that it > can be exported safely, it should be treated as a unexportable, in > the same way we treat procfs and sysfs. > This sounds more like an NFS server problem than a client side NFS. Can we add support to the client side NFS and let server that think that they can handle XATTR implement it? We should probably start a discussion in the IETF to resolve the issues you see with XATTR at least for NFSv4.3. Marc. > Cheers > Trond--