mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Frodo Looijaard <frodol@dds.nl>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: PATCH to access old-style FAT fs
Date: Tue, 27 Jan 2004 21:55:34 +0900	[thread overview]
Message-ID: <87n0898sah.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <bv3qb3$4lh$1@terminus.zytor.com>

"H. Peter Anvin" <hpa@zytor.com> writes:

> Followup to:  <20040126173949.GA788@frodo.local>
> By author:    Frodo Looijaard <frodol@dds.nl>
> In newsgroup: linux.dev.kernel
> > 
> > Hi folks,
> > 
> > I have created and attached a new version of my old-style FAT filesystem
> > patch, this time for the 2.6.0 kernel. It can also be found on
> > http://debian.frodo.looijaard.name/. 
> > 
> > Some old implementation of the FAT standard mark the end of the
> > directory file index by inserting a filename beginning with a byte 00.
> > All entries after it should be ignored, even though they are not marked
> > as deleted. At least some EPOC releases (an OS used on Psion PDAs, for
> > example) still use this policy.
> > 
> 
> It's not just "old implementations" -- it's the spec.
> 
> After reaching a filename beginning with 00, no further data should be
> assumed to be in that filesystem.  MS-DOS itself would only do that
> when formatting the filesystem, so *all* the subsequent entries would
> be assumed to start with 00, but that doesn't really seem to be to
> spec.

The new cluster for directory entries must be initialized by 0x00.
And, when the directory entry is deleted, the name[0] is updated by
0xe5 not 0x00.

So, if the name[0] is 0x00, it after, all bytes in cluster is 0x00.

The fat driver can stop at name[0] == 0x00, but this is just optimization.
The behavior shouldn't change by this.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2004-01-27 12:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-26 17:39 Frodo Looijaard
2004-01-26 19:38 ` H. Peter Anvin
2004-01-27 12:55   ` OGAWA Hirofumi [this message]
2004-01-27 18:51     ` H. Peter Anvin
2004-01-27 20:17       ` OGAWA Hirofumi
2004-01-28 11:56         ` Frodo Looijaard
2004-01-28 20:08           ` OGAWA Hirofumi
2004-01-28 20:24             ` Frodo Looijaard
2004-01-28 21:01               ` OGAWA Hirofumi
2004-01-29 10:56                 ` Frodo Looijaard
2004-01-31  2:19                   ` H. Peter Anvin
2004-01-31 17:19                     ` OGAWA Hirofumi
2004-01-29 22:39                 ` Frodo Looijaard
2004-01-29 22:49                   ` H. Peter Anvin
2004-01-30  0:30                   ` Andries Brouwer
2004-01-30  3:40                   ` OGAWA Hirofumi
2004-02-01 14:51                   ` Frodo Looijaard

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=87n0898sah.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=frodol@dds.nl \
    --cc=hpa@zytor.com \
    --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

Powered by JetHome