xfs
[Top] [All Lists]

Re: [PATCH v13 21/51] ext4: Add richacl feature flag

To: Andreas Dilger <adilger@xxxxxxxxx>
Subject: Re: [PATCH v13 21/51] ext4: Add richacl feature flag
From: Andreas Gruenbacher <agruenba@xxxxxxxxxx>
Date: Wed, 4 Nov 2015 03:43:31 +0100
Cc: Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>, "Theodore Ts'o" <tytso@xxxxxxx>, Andreas Dilger <adilger.kernel@xxxxxxxxx>, "J. Bruce Fields" <bfields@xxxxxxxxxxxx>, Jeff Layton <jlayton@xxxxxxxxxxxxxxx>, Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx>, Anna Schumaker <anna.schumaker@xxxxxxxxxx>, Dave Chinner <david@xxxxxxxxxxxxx>, linux-ext4 <linux-ext4@xxxxxxxxxxxxxxx>, XFS Developers <xfs@xxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, Linux NFS Mailing List <linux-nfs@xxxxxxxxxxxxxxx>, linux-cifs@xxxxxxxxxxxxxxx, Linux API <linux-api@xxxxxxxxxxxxxxx>, "Aneesh Kumar K.V" <aneesh.kumar@xxxxxxxxxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat_com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=EAff2Tri6RIcnnO0arbcjYPs/SE+xiEu1cV8isM93sA=; b=OMORgaFxonv/sCpJ2oH8Sm5A88ScKEbnGj9JqvU9rLdxw+VAhari8y+TSZwQKLTYy/ Jnkc6rAlyto3ghPn2z9Q6JkXzP4ZYAgaNZHsJ/RxD8o37Mr/KLM6NzfE7BpIyEl/66lo XWtZxoPNgMGqWljKKa0DHlIWD45GSTV2kkCNObLkMGUdFgXiiOWebDEW/eOdJYo2S8/h mVQooZIXEqa0Q5GOtocwuybSZE6nQ3Yqh2hsKPxdk3JnFYIEnpVyHbsEvg1aMs/EeBkj G0mQZ5qZeSK4b9AtBmINDz2/JEMECqMue59RK+kSoDziVK4s9iJq/CC0BP7bpVeClhBa ZKyw==
In-reply-to: <CAHc6FU46EuDQ0S9TPYuLosHvppsqcqOF_oxxgTFHr+uXj59Drg@xxxxxxxxxxxxxx>
References: <1446563847-14005-1-git-send-email-agruenba@xxxxxxxxxx> <1446563847-14005-22-git-send-email-agruenba@xxxxxxxxxx> <06282344-726E-49AD-936B-7BFF8F43B967@xxxxxxxxx> <CAHc6FU46EuDQ0S9TPYuLosHvppsqcqOF_oxxgTFHr+uXj59Drg@xxxxxxxxxxxxxx>
On Wed, Nov 4, 2015 at 3:28 AM, Andreas Gruenbacher <agruenba@xxxxxxxxxx> wrote:
> It's the commit message that's misleading here, I'll fix it.

Commit message changed to:

    This feature flag selects richacl instead of POSIX ACL support on the
    filesystem.  When this feature is off, the "acl" and "noacl" mount options
    control whether POSIX ACLs are enabled.  When it is on, richacls are
    automatically enabled and using the "noacl" mount option leads to an error.

Thanks,
Andreas

<Prev in Thread] Current Thread [Next in Thread>