Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755782AbZGBXqt (ORCPT ); Thu, 2 Jul 2009 19:46:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753262AbZGBXqg (ORCPT ); Thu, 2 Jul 2009 19:46:36 -0400 Received: from sovereign.computergmbh.de ([85.214.69.204]:39934 "EHLO sovereign.computergmbh.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753247AbZGBXqf (ORCPT ); Thu, 2 Jul 2009 19:46:35 -0400 Date: Fri, 3 Jul 2009 01:46:37 +0200 (CEST) From: Jan Engelhardt To: Theodore Tso cc: Alan Cox , Rusty Russell , Pavel Machek , tridge@samba.org, OGAWA Hirofumi , john.lanza@linux.com, Linux Kernel Mailing List , linux-fsdevel@vger.kernel.org, Dave Kleikamp , corbet@lwn.net, jcm@jonmasters.org Subject: Re: CONFIG_VFAT_FS_DUALNAMES regressions In-Reply-To: Message-ID: References: <19013.8005.541836.436991@samba.org> <20090630063102.GB1351@ucw.cz> <200907012019.53932.rusty@rustcorp.com.au> <20090701122558.3a7c80d3@lxorguk.ukuu.org.uk> <20090701140503.GA21185@mit.edu> User-Agent: Alpine 2.00 (LSU 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2144 Lines: 51 On Friday 2009-07-03 01:17, Jan Engelhardt wrote: > >On Wednesday 2009-07-01 16:05, Theodore Tso wrote: >>On Wed, Jul 01, 2009 at 12:25:58PM +0100, Alan Cox wrote: >> >>> (most *FAT using products don't use Microsofts >>> implementation). Testing it versus Windows and saying it works is >>> not really adequate. Thats what ACPI and BIOS people do that *we* >>> moan about all the time. >> >>[...] >>The other big user I can think of are digital cameras, but (a) >>normally most users read from them and then delete the pictures, and >>rarely write to media meant for a digital camera, and (b) the DCIM >>standard for digital cameras explicitly only supports 8.3 filenames >>and so digital camera manufacturers explicitly don't need to deal with >>Long File Names at all. (Hmm.... I wonder why....) >>[...] >>Ultimately, though, requiring that every single possible device be >>tested is probably not reasonable, so the best way to do this testing >>is the way do most of our testing; we do basic due diligence, but then >>we merge it into mainline and let our huge user community try it out. > > >Yes, here is your precedent case. The DUALNAMES patch breaks the >operation on my Fujifilm Finepix A210 digital camera. Adding to that, I've just run it against every possible USB device I could dig up in my room (i.e. one more for now). It also breaks with the Tekmax T-1000/TMP-1000 (nicknamed "ioneit"/"i-one-it"/"i-want-it") digital audio player. Its built-in directory browser does display the copied file (see below), but does not want to play it nor enqueue it into the playlist. Again, a simple copy operation was performed — this time for both 8.3 and long names, i.e.: $ cp working.mp3 TEST0000.mp3 $ cp working.mp3 TEST12345678.mp3 None of the dualnames=n-created files were accepted. (Combinations that worked: 2.6.29.5-w/o-dualnames-patch, and 2.6.31-rc1+dualnames=y) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/