| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [XFSTESTS 5/6] Add richacl tests |
| From: | Andreas Gruenbacher <agruenba@xxxxxxxxxx> |
| Date: | Tue, 15 Dec 2015 00:32:10 +0100 |
| Cc: | XFS Developers <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20151208064410.GD19802@dastard> |
| References: | <1447856269-7872-1-git-send-email-agruenba@xxxxxxxxxx> <1447856269-7872-6-git-send-email-agruenba@xxxxxxxxxx> <20151123230847.GH26718@dastard> <CAHc6FU4BDRqTM6dMONtyb98YqHSVp5M=GYnJ+k7EQRVNPvrQNA@xxxxxxxxxxxxxx> <20151207211156.GD26718@dastard> <CAHc6FU4X+7rPtR8LE9W4HZv2UGsZ-+1zHSq5X5sFgVQmL5mCqQ@xxxxxxxxxxxxxx> <20151208064410.GD19802@dastard> |
On Tue, Dec 8, 2015 at 7:44 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote: > So you have to mkfs the filesytem, then mount it, then you can run > getfattr to check if richacls are supported. Yet mkfs can fail, the > mount can fail, and neither of them are going to give you nice > "richacls not supported" errors. See xfs/191, again. Okay, if the richacl tests should run on a scratch filesystem, then we can obviously test if a richacl filesystem can be created and mounted and we won't have to test if the mounted filesystem supports richacls. It then also makes sense to run all of the richacl tests at once, on the same scratch file system, similar to xfs/191. Thanks, Andreas |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH v4 4/7] dax: add support for fsync/sync, Ross Zwisler |
|---|---|
| Next by Date: | Re: [XFSTESTS 5/6] Add richacl tests, Andreas Gruenbacher |
| Previous by Thread: | Re: [XFSTESTS 5/6] Add richacl tests, Dave Chinner |
| Next by Thread: | Re: [XFSTESTS 5/6] Add richacl tests, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |