On Monday 13 August 2007 01:14, Evgeniy Polyakov wrote:
> > Oops, and there is also:
> >
> > 3) The bio throttle, which is supposed to prevent deadlock, can
> > itself deadlock. Let me see if I can remember how it goes.
> >
> > * generic_make_request puts a bio in flight
> > * the bio gets past the throttle and initiates network IO
> > * net calls sk_alloc->alloc_pages->shrink_caches
> > * shrink_caches submits a bio recursively to our block device
> > * this bio blocks on the throttle
> > * net may never get the memory it needs, and we are wedged
>
> If system is in such condition, it is already broken - throttle limit
> must be lowered (next time) not to allow such situation.
Agreed that the system is broken, however lowering the throttle limit
gives no improvement in this case.
This is not theoretical, but a testable, repeatable result.
Instructions to reproduce should show up tomorrow.
This bug is now solved in a kludgy way. Now, Peter's patch set offers a
much cleaner way to fix this little problem, along with at least one
other nasty that it already fixed.
Regards,
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
