| To: | Andreas Gruenbacher <agruenba@xxxxxxxxxx> |
|---|---|
| Subject: | Re: xfsprogs-dev: Richacl support |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Sun, 18 Oct 2015 10:02:24 +1100 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CAHc6FU65zy+rDCWapURLr-cApi7b40OhfB7bQK0iC0r_6Wn_qg@xxxxxxxxxxxxxx> |
| References: | <CAHc6FU65zy+rDCWapURLr-cApi7b40OhfB7bQK0iC0r_6Wn_qg@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Fri, Oct 16, 2015 at 05:44:42PM +0200, Andreas Gruenbacher wrote: > Hello, > > could the richacl feature flag please be added to xfsprogs so that we > won't end up with incompatible file systems? > > https://github.com/andreas-gruenbacher/xfsprogs-dev Can you post patches so we can review them in the normal manner? > Also, should this really be an incompatible feature flag? Mounting a > richacl filesystem on a kernel without richacl support would otherwise > work but it could grant unwanted access to files. You answered that question yourself here: :) http://oss.sgi.com/archives/xfs/2015-10/msg00357.html i.e. INCOMPAT is fine, becuse RO_INCOMPAT results in unpredictable and incompatible behaviour from the user perspective... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: e2fsprogs: Richacl support, Dave Chinner |
|---|---|
| Next by Date: | Re: [PATCH v11 21/48] ext4: Add richacl feature flag, Dave Chinner |
| Previous by Thread: | xfsprogs-dev: Richacl support, Andreas Gruenbacher |
| Next by Thread: | FW: IT Helpdesk Request, Cunningham, Stacy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |