From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com ([66.111.4.26]:58811 "EHLO out2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751596AbcHIADc convert rfc822-to-8bit (ORCPT ); Mon, 8 Aug 2016 20:03:32 -0400 From: Nikolaus Rath To: Seth Forshee Cc: fuse-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org, Miklos Szeredi , "Eric W. Biederman" , Michael j Theall , Jean-Pierre =?utf-8?Q?Andr=C3=A9?= Subject: Re: [RFC v3 0/2] Support for posix acls in fuse References: <1470086846-19844-1-git-send-email-seth.forshee@canonical.com> Date: Mon, 08 Aug 2016 17:03:30 -0700 In-Reply-To: <1470086846-19844-1-git-send-email-seth.forshee@canonical.com> (Seth Forshee's message of "Mon, 1 Aug 2016 16:27:24 -0500") Message-ID: <874m6u3j1p.fsf@thinkpad.rath.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Aug 01 2016, Seth Forshee wrote: > - Remove passthrough of acl xattrs when fuse acl support is disabled or > default_permissions is not used. > > This last change is user visible, but as fuse filesystems cannot > meaninfully support acls today it's not really a regression. Are you sure about that? I believe there are FUSE file systems out there that are parsing/constructing the kernel's xattr representation and (together with no_default_permissions) support ACLs. Or is there another problem? Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«