All of lore.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH to access old-style FAT fs
Date: Sun, 01 Feb 2004 02:19:54 +0900	[thread overview]
Message-ID: <87hdycujb9.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <bvf3b3$6pr$2@terminus.zytor.com>

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

> This is of course dangerous, since it could create conflicts.
> 
> Thus, I suggest we do write new 0x00 markers; even though it's not
> required (it only matters if the filesystem is out of spec and
> therefore by definition corrupt), it would help the Psion, and
> wouldn't cause any problems for in-spec filesystems.

Yes, that cluster is dangerous. However, repair should be fsck's
job. IMO, for repair we shouldn't add unneeded I/O to normal path.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2004-01-31 17:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-26 17:39 PATCH to access old-style FAT fs Frodo Looijaard
2004-01-26 19:38 ` H. Peter Anvin
2004-01-27 12:55   ` OGAWA Hirofumi
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 [this message]
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=87hdycujb9.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --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 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.