> On Mon, 26 May 2008 12:53:18 -0400
> Pete Wyckoff <pw@osc.edu> wrote:
>
> > I finally got around to testing the set of lifetime management
> > fixes you applied. This is 2.6.26-rc3 with some varlen, bidi,
> > iser patches, and iovec on bsg, but nothing that should affect
> > the locking.
> >
> > I can confirm that the first two of these three old bugs are
> > no longer reproducable:
> >
> >
http://marc.info/?l=linux-scsi&m=120508166505141&w=2
> >
http://marc.info/?l=linux-scsi&m=120508177905365&w=2
> >
http://marc.info/?l=linux-scsi&m=120508178005376&w=2
> >
> > Thanks! The third, however, is a hang that still can happen. But
> > it is very obscure and requires a bit of timing to get right. As a
> > reminder, here's the setup, and updated traces.
>
> Ah, sorry about it. I didn't understand the third correctly.
>
>
> > Maybe it is necessary to split up that bsg_mutex to use multiple
> > finer-grained locks.
>
> We could but we use bsg_mutex to protect bsg_device_list and idr. So I
> think that we don't need hold bsg_mutex during
> bsg_complete_all_commands. How about this?
>
>
> diff --git a/block/bsg.c b/block/bsg.c
> index f0b7cd3..d81104e 100644
> --- a/block/bsg.c
> +++ b/block/bsg.c