> >Ok, lets see. Random process does lock_super and then writes too much
> >data (=> wakeup_bdflush). Ok, now superblock is locked and bdflush is
>
> If kflushd would lockup in lock_super you wouldn't see down_failed but you
> would only block in __wait_on_super().
Any idea what might cause blocking in down_failed?
BTW I've seen kflushd blocked in wait_on_super once, too.
> >called. But due to loop, bdflush tries to write to sparse block, which
>
> BTW, the last time I checked I noticed that the loop may also cause
> deadlocks due out of request slots :(. The workaround with WRITEA in
> bdflush seems to me only a way to hide such deadlock.
Hmm, great. Any chance to fix loop?
There's person listed in CREDITS for "making loop work on sparse
files". I'd like to mtalk to him but adres in credits is invalid.
Pavel
-- The best software in life is free (not shareware)! Pavel GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/