Re: loop device deadlocks

From: Mike Galbraith (
Date: Sun Jun 18 2000 - 09:21:42 EST

On Sun, 18 Jun 2000, Steve Dodd wrote:

> On Sat, Jun 17, 2000 at 05:44:31PM +0200, Mike Galbraith wrote:
> > I still think that it's reentering to service the same blocks it's already
> > trying to service, but am not sure about that.
> No, that shouldn't happen - the buffer will get locked when we start I/O on it.

(one printk right about here aught to... well _that_ kinda sucks)

In ac20 at least (virtual loophole;) you're 100% right.

> I believe the problem is this:

If the thing isn't fixed by the time I get a chance to tinker with
it again, I'll try looking at it from _your_ angle.


all those hours reading traces and whatnot and you never check the
fscking request bh. <kick kick kick>

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:15 EST