* [Fwd: PATCH for Corrupted IO on all block devices]
@ 2001-07-18 1:23 David J. Picard
0 siblings, 0 replies; only message in thread
From: David J. Picard @ 2001-07-18 1:23 UTC (permalink / raw)
To: axboe, linux-kernel
"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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2001-07-18 1:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-07-18 1:23 [Fwd: PATCH for Corrupted IO on all block devices] David J. Picard
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).