Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp3437930ybx; Sun, 3 Nov 2019 19:06:08 -0800 (PST) X-Google-Smtp-Source: APXvYqxoiIglpMpT7IgtZjsA8A1zaScEqMmbuu5lUysekEpqDAAjeu/U6P5JxatMH/xXu+NdUpcK X-Received: by 2002:a17:906:a388:: with SMTP id k8mr19309199ejz.223.1572836768172; Sun, 03 Nov 2019 19:06:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1572836768; cv=none; d=google.com; s=arc-20160816; b=vPuLGjmF5Dl63D8cDra2RTSoRiJTD34tTkj9J32bk8H5FCz51ux7gJgQAWAw2VlgHa 7GpMCLCNwjvfYFBqw/hbVUfVp9Kj3AWvekwknTZjBau3zqqALNqa4C1eZDEU3q+QMNAh mMLkHIF7EfX+vuHtSmWUasK5Pw8jufKgeVZZ8QScW33f39qJzsxWoRzyt7vBOIybuYYk yH1Xaw3cB6C6T5P1SHzLasx6ZuUE632Db9BRzGBCaNQij7E4dRni820U7LPTgsF10+vE n+IL6a/czddMHeS9p6s657+PqqVmRFzr+IOEAXSyKSOnI4OSWastSUCMYe5fMoDbIr6y 4RwA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:from:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:date; bh=I0lwhIusSZGKjJPkWrIWQ8BonoXiGR7HxBlXxUOvx+k=; b=Rn7BD1Z2XRmDYXyDlRUmATeCTT3pmT4ryIWl2MkOrUFWw1UqijfQEpEZ/L0BVyIgCX 9/61hRloKLu+exVe7bhpRHrHONZWWSn3ysWEK0ZWITapv9GcwjxgmCe/ie4DylszfJak 116azAGg9BZf0v56fiXjKDwUDkOmvz/VK8kSbuq6H+8vzZDv7nn9G5XvZzjZuKfXlCDk 00h+MaPOA1zkgi1NmiD4YTjKw9SVHocTxxBic0kne64YTPtHSfoqS7GXsYqfCSj7nwFa N2oNxxAQejL+eNhqY/tXD1H7tm+RaOg9/F6DphBSrscbMj9Gjgkvp9RWeWGEVng+9rVb GECw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d6si7100754ede.119.2019.11.03.19.05.29; Sun, 03 Nov 2019 19:06:08 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728876AbfKDDBd (ORCPT + 99 others); Sun, 3 Nov 2019 22:01:33 -0500 Received: from fieldses.org ([173.255.197.46]:59146 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728643AbfKDDBc (ORCPT ); Sun, 3 Nov 2019 22:01:32 -0500 Received: by fieldses.org (Postfix, from userid 2815) id 3ECB71C19; Sun, 3 Nov 2019 22:01:32 -0500 (EST) Date: Sun, 3 Nov 2019 22:01:32 -0500 To: Chuck Lever Cc: Frank van der Linden , Linux NFS Mailing List , linux-fsdevel@vger.kernel.org Subject: Re: [RFC PATCH 00/35] user xattr support (RFC8276) Message-ID: <20191104030132.GD26578@fieldses.org> References: <9CAEB69A-A92C-47D8-9871-BA6EA83E1881@gmail.com> <20191024231547.GA16466@dev-dsk-fllinden-2c-c1893d73.us-west-2.amazon.com> <18D2845F-27FF-4EDF-AB8A-E6051FA03DF0@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18D2845F-27FF-4EDF-AB8A-E6051FA03DF0@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) From: bfields@fieldses.org (J. Bruce Fields) Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On Fri, Oct 25, 2019 at 03:55:09PM -0400, Chuck Lever wrote: > > On Oct 24, 2019, at 7:15 PM, Frank van der Linden wrote: > > I think both of these are cases of being careful. E.g. don't enable > > something by default and allow it to be disabled at runtime in > > case something goes terribly wrong. > > > > I didn't have any other reasons, really. I'm happy do to away with > > the CONFIG options if that's the consensus, as well as the > > nouser_xattr export option. > > I have similar patches adding support for access to a couple of > security xattrs. I initially wrapped the new code with CONFIG > but after some discussion it was decided there was really no > need to be so cautious. > > The user_xattr export option is a separate matter, but again, > if we don't know of a use case for it, I would leave it out for > the moment. Agreed. Do ext4, xfs, etc. have an option to turn off xattrs? If so, maybe it would be good enough to turn off xattrs on the exported filesystem rathre than on the export. If not, maybe that's a sign that hasn't been a need. --b.