From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 5/7] XFS: Unicode case-insensitive lookup implementation Date: Thu, 3 Apr 2008 18:31:42 -0400 Message-ID: <20080403223142.GA24451@infradead.org> References: <20080402062508.017738664@chook.melbourne.sgi.com> <20080402062709.011126702@chook.melbourne.sgi.com> <20080403171450.GB22385@infradead.org> <20080403222059.GU103491721@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , Barry Naujok , xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org To: David Chinner Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:59576 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751198AbYDCWbo (ORCPT ); Thu, 3 Apr 2008 18:31:44 -0400 Content-Disposition: inline In-Reply-To: <20080403222059.GU103491721@sgi.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Apr 04, 2008 at 08:20:59AM +1000, David Chinner wrote: > On Thu, Apr 03, 2008 at 01:14:50PM -0400, Christoph Hellwig wrote: > > Validating file names is not the filesystem job. In fact it's utterly > > stupid, a unix filename is a sequence of bytes without special meaning > > except for ., .., / and \0 > > So you're suggesting that we should rely on userspace being bug free > and always only using valid unicode sequences in it's names? just treat invalid unicode sequences as plain blob.