> Hmm, it seems to me the loop device buffers shouldn't be locked until
> all the resources have been rounded up. But if this is what's being
> done, it's easy enough to add a test not to wait on a loop buffer.
>
> Are there any other cases of locked buffers that won't unlock on their
> own when the i/o completes?
RAID-4/5 completes I/O from within a private kernel thread and not
from an interrupt context, so that wait_on_buffer()/schedule()/etc
is OK, but no RAID buffers will be unlocked during a busy loop.
Gadi