> On Thu, 22 Apr 1999, Alexander Viro wrote:
>
> > What the... Wait a bit. How and when can ->b_list become *not*
> >corrsponding to the list where the buffer sits, anyway?
>
> Think if nextbh is a clean buffer not belonging to the dev that is
> changing blocksize.
Oh, I see. The problem being not that we can get the buffer on the
wrong list but that we can wander into the wrong list ourselves...
Ho-hummm... Methink your solution is wrong, though. Better one:
do non-blocking scan of the lists, gathering the stuff that
should die into the separate (local) list.
while the list is non-empty
pick the first buffer,
wait_on_buffer
move it to free list.
Comments? I'm more worried about the loop device handling...
-
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/