All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Herbrechtsmeier <stefan.herbrechtsmeier-oss@weidmueller.com>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de,
	Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>,
	Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH] fs: fat: do not mangle short filenames
Date: Wed, 22 Mar 2023 09:51:32 +0100	[thread overview]
Message-ID: <c9b9bea5-337e-2b66-fa52-52dab9e609af@weidmueller.com> (raw)
In-Reply-To: <20230321155404.GX8135@bill-the-cat>

Am 21.03.2023 um 16:54 schrieb Tom Rini:
> On Tue, Mar 21, 2023 at 04:53:22PM +0100, Stefan Herbrechtsmeier wrote:
>> Am 21.03.2023 um 16:35 schrieb Tom Rini:
>>> On Tue, Mar 21, 2023 at 08:43:07AM +0100, Stefan Herbrechtsmeier wrote:
>>>> Am 20.03.2023 um 18:01 schrieb Tom Rini:
>>>>> On Fri, Mar 17, 2023 at 01:04:13PM +0100, Stefan Herbrechtsmeier wrote:
>>>>>
>>>>>> From: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
>>>>>>
>>>>>> Do not mangle lower or mixed case filenames which fit into the upper
>>>>>> case 8.3 short filename. This ensures FAT standard compatible short
>>>>>> filenames (SFN) to support systems without long filename (LFN) support
>>>>>> like boot roms (ex. SFN BOOT.BIN instead of BOOT~1.BIN for LFN
>>>>>> boot.bin).
>>>>>>
>>>>>> Signed-off-by: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>
>>>>>>
>>>>>> ---
>>>>>>
>>>>>>     fs/fat/fat_write.c | 11 +++++++----
>>>>>>     1 file changed, 7 insertions(+), 4 deletions(-)
>>>>> Can we update test/py/tests/test_fs/ somewhere to have a test for this
>>>>> case? Thanks.
>>>> What is the recommended approach to test internal behavior? The short name
>>>> isn't avialable at the terminal because u-boot support VFAT.
>>> Well, you triggered this problem with a filesystem that had contents
>>> that were "just so" and then didn't work as expected, yes?
>>
>> No, I write a file to a file system and the boot rom do not find the file
>> because the name was wrong (BOOT~1.BIN instead of BOOT.BIN).
>>
>> The mdir command shows the short and long file name. I will add a
>> test_fat.py with a test.
> Ah, ok, and great, thanks!


I have send a separate patch `test: fs: Check fat short file name` or 
should I send a new series with both patches?

Regards
   Stefan


  reply	other threads:[~2023-03-22  8:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 12:04 [PATCH] fs: fat: do not mangle short filenames Stefan Herbrechtsmeier
2023-03-20 17:01 ` Tom Rini
2023-03-21  7:43   ` Stefan Herbrechtsmeier
2023-03-21 15:35     ` Tom Rini
2023-03-21 15:53       ` Stefan Herbrechtsmeier
2023-03-21 15:54         ` Tom Rini
2023-03-22  8:51           ` Stefan Herbrechtsmeier [this message]
2023-03-22 13:20             ` Tom Rini
2023-03-31 14:15 ` Tom Rini

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=c9b9bea5-337e-2b66-fa52-52dab9e609af@weidmueller.com \
    --to=stefan.herbrechtsmeier-oss@weidmueller.com \
    --cc=sjg@chromium.org \
    --cc=stefan.herbrechtsmeier@weidmueller.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.