All of lore.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Sancho Dauskardt <sda@bdit.de>, linux-kernel@vger.kernel.org
Subject: Re: FAT statfs loop abort on read-error
Date: Tue, 08 Jul 2003 00:54:48 +0900	[thread overview]
Message-ID: <87u19ypc1j.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20030706102410.2becd137.rddunlap@osdl.org>

"Randy.Dunlap" <rddunlap@osdl.org> writes:

> On Fri, 04 Jul 2003 13:57:19 +0200 Sancho Dauskardt <sda@bdit.de> wrote:
> |   when calling statfs on a volume that has been removed (without umount) 
> | fat_statfs() will attempt to read all sectors of the fat table quite a few 
> | times (depending on the fat type, eg. FAT16 --> 256 times).

Yes, fat driver of 2.4 ignore the many errors.

> | Possible solution:
> | 1. let default_fat_access return something like -2 on 'can't read' error.
> | 2. Abort stafs loop on error.
> | 3. return -EIO
> | 
> | This would break mode fat_access calls. I could make a patch, but I don't 
> | know what's going on with those cvf extensions (which seem to replace 
> | fat_access). Is dmsdos dead / can we ignore it ?
> | Somewhere in the list archives, I found comments about the cvf stuff being 
> | completely removed ?

I don't know anybody ported dmsdos to 2.4. The cvf stuff was removed
and many error handlings was fixed on 2.5.x. So, personally I think to
remove the cvf stuff and backport the some parts of fat driver to 2.4
is good.

> (I asked him to add a patch to MAINTAINTERS...)

Thank you. But honestly, I may not have skill enough.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2003-07-07 15:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-04 11:57 FAT statfs loop abort on read-error Sancho Dauskardt
2003-07-06 17:24 ` Randy.Dunlap
2003-07-07 15:54   ` OGAWA Hirofumi [this message]
2003-07-07 16:24     ` Christoph Hellwig
2003-07-08 12:18       ` OGAWA Hirofumi
2003-07-08 12:33         ` Christoph Hellwig
2003-07-08 14:56           ` OGAWA Hirofumi
2003-07-07 16:38     ` Jeff Garzik
2003-07-08 12:29     ` Sancho Dauskardt
2003-07-08 14:46       ` OGAWA Hirofumi
2003-09-11 20:47         ` Sancho Dauskardt
2003-09-12 17:12           ` OGAWA Hirofumi

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=87u19ypc1j.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=sda@bdit.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.