Message-ID: <3B54E4FA.DE090D0D@psind.com>
Date: Tue, 17 Jul 2001 21:23:06 -0400
From: "David J. Picard" <dave@psind.com>
Reply-To: dpicard@rcn.com
MIME-Version: 1.0
To: axboe@suse.de, linux-kernel@vger.kernel.org
Subject: [Fwd: PATCH for Corrupted IO on all block devices]
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

"David J. Picard" wrote:
> 
> This is happening on an e2fs file system, I haven't tried it with
> others, but the code is pretty clear in elevator.c about putting the
> reads ahead of the write if they are pushed into the queue close enough
> to each other.
> 
> Linus Torvalds wrote:
> >
> > On Tue, 17 Jul 2001, David J. Picard wrote:
> > >
> > > Basically, what is happening is the read requests are being pushed to
> > > the front of the IO queue - before the preceding write for the same
> > > sector.
> >
> > This is a bug in the USER, not in the code.
> >
> > The locking is NOT supposed to be done at the elevator level (or, indeed
> > at ANY _io_ level), but must be done by upper layers.
> >
> > If upper layers do not do this locking, then THAT is the bug.
> >
> > What filesystem do you see the bug with?
> >
> >                 Linus
> 
> --
> David J. Picard
>   dave@psind.com
> 
> If you can keep your head when all about you are losing theirs,
>   then you clearly don't understand the situation.

-- 
David J. Picard
  dave@psind.com

If you can keep your head when all about you are losing theirs,
  then you clearly don't understand the situation.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/