| To: | Ben Myers <bpm@xxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 05/16] xfs: return the first match during case-insensitive lookup. |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Tue, 7 Oct 2014 09:19:28 +1100 |
| Cc: | linux-fsdevel@xxxxxxxxxxxxxxx, olaf@xxxxxxx, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20141003215542.GD1865@xxxxxxx> |
| References: | <20141003214758.GY1865@xxxxxxx> <20141003215542.GD1865@xxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Fri, Oct 03, 2014 at 04:55:42PM -0500, Ben Myers wrote: > From: Olaf Weber <olaf@xxxxxxx> > > Change the XFS case-insensitive lookup code to return the first match > found, even if it is not an exact match. Whether a filesystem uses > case-insensitive lookups is determined by a superblock bit set during > filesystem creation. This means that normal use cannot create two files > that both match the same filename. > > Signed-off-by: Olaf Weber <olaf@xxxxxxx> This is really dependent on whether we want to support mixed CI/non-CI filesystems, yes? i.e. if we want to support mixed case setups, then we need to keep the code as it stands? What is the downside of keeping the code unchaged and our options open? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 08/16] xfs: change interface of xfs_nameops.hashname, Dave Chinner |
|---|---|
| Next by Date: | Re: Question about services, Carlos Maiolino |
| Previous by Thread: | [PATCH 05/16] xfs: return the first match during case-insensitive lookup., Ben Myers |
| Next by Thread: | Re: [PATCH 05/16] xfs: return the first match during case-insensitive lookup., Ben Myers |
| Indexes: | [Date] [Thread] [Top] [All Lists] |