From mboxrd@z Thu Jan 1 00:00:00 1970 From: tridge@samba.org Subject: Re: [PATCH] Added CONFIG_VFAT_FS_DUALNAMES option Date: Mon, 29 Jun 2009 07:28:12 +1000 Message-ID: <19015.57452.966688.694057@samba.org> References: <19013.8005.541836.436991@samba.org> <19014.54044.484370.187018@samba.org> <19015.482.794111.612472@samba.org> <87ab3sx4ch.fsf@devron.myhome.or.jp> Reply-To: tridge@samba.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: john.lanza@linux.com, linux-kernel@vger.kernel.org, OGAWA Hirofumi , linux-fsdevel@vger.kernel.org, Dave Kleikamp , Steve French , Mingming Cao , Paul McKenney To: ebiederm@xmission.com (Eric W. Biederman) Return-path: Received: from mail.samba.org ([66.70.73.150]:49939 "EHLO lists.samba.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752054AbZF1V2Z (ORCPT ); Sun, 28 Jun 2009 17:28:25 -0400 In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hi Eric, > Tridge. Is there any reason to believe that Microsoft will continue > to treat Longfilenames without short filenames as valid in vfat? I'd be quite surprised if they deliberately changed their VFAT code to break Linux with this patch. I'd say it is more likely that once Linux kernels with this change are in widespread use that Microsoft will start to test any changes in their VFAT filesystem to make sure it works with Linux with this patch. > It wouldn't even surprise me if you haven't seen such shenanigans > while working on samba. In recent times Microsoft has been testing new OS releases against Samba, and has been actively working with the Samba Team to try to prevent breakages with new releases. That doesn't mean the scenario you describe is impossible, it just means it isn't as likely as perhaps it once was. Cheers, Tridge