From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Chinner Subject: Re: [PATCH 05/16] xfs: return the first match during case-insensitive lookup. Date: Tue, 7 Oct 2014 09:19:28 +1100 Message-ID: <20141006221928.GJ2301@dastard> References: <20141003214758.GY1865@sgi.com> <20141003215542.GD1865@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, olaf@sgi.com, xfs@oss.sgi.com To: Ben Myers Return-path: Content-Disposition: inline In-Reply-To: <20141003215542.GD1865@sgi.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com List-Id: linux-fsdevel.vger.kernel.org On Fri, Oct 03, 2014 at 04:55:42PM -0500, Ben Myers wrote: > From: Olaf Weber > > 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 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@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs