mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Marton Balint <cus@fazekas.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: vfat creates multiple files with the same filename
Date: Wed, 01 Jul 2009 09:29:34 +0900	[thread overview]
Message-ID: <87y6r9dz4h.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <Pine.LNX.4.64.0907010158560.835@cinke.fazekas.hu> (Marton Balint's message of "Wed, 1 Jul 2009 02:02:53 +0200 (CEST)")

Marton Balint <cus@fazekas.hu> writes:

> On Tue, 30 Jun 2009, OGAWA Hirofumi wrote:
>> Marton Balint <cus@fazekas.hu> writes:
>> 
>> > I don't know if removing the invalid characters silently instead of 
>> > returning EINVAL is a good practice, but allowing two files with identical 
>> > filenames is definitely wrong. 
>> 
>> The utf8 function seems didn't return the error for invalid char.
>> 
>> > Could someone please have a look at the problem? Unfortunately I am not 
>> > qualified enough to track it down...
>> >
>> > I've run the testcase on both 2.6.30 and 2.6.31-rc1 kernels, but this bug 
>> > is probably not very new, since I remember having it also in 2.6.27.
>> 
>> This is quick hack though, this should return -EINVAL for invalid char
>> like nls.  Can you try this?
>
> It works for me, filenames with invalid utf-8 characters are now rejected, 
> so I no longer can create multiple files with the same name. Thanks for 
> the fix.

Thanks for testing.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2009-07-01  0:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-28 18:26 Marton Balint
2009-06-30  2:24 ` OGAWA Hirofumi
2009-07-01  0:02   ` Marton Balint
2009-07-01  0:29     ` OGAWA Hirofumi [this message]
2009-07-06 19:11       ` Marton Balint

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y6r9dz4h.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=cus@fazekas.hu \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®