Re: Manual driver binding and unbinding broken for SCSI

2017-02-22 Thread Ming Lei
On Wed, Feb 22, 2017 at 1:14 AM, Jan Kara wrote: > On Sun 19-02-17 18:19:58, Omar Sandoval wrote: >> On Fri, Feb 17, 2017 at 04:43:56PM -0800, James Bottomley wrote: >> > This seems to be related to a 0day test we got on the block tree, >> > details here: >> > >> >

Re: Manual driver binding and unbinding broken for SCSI

2017-02-21 Thread Jan Kara
On Sun 19-02-17 18:19:58, Omar Sandoval wrote: > On Fri, Feb 17, 2017 at 04:43:56PM -0800, James Bottomley wrote: > > This seems to be related to a 0day test we got on the block tree, > > details here: > > > > http://marc.info/?t=14862406881 > > > > I root caused the above to something not

Re: Manual driver binding and unbinding broken for SCSI

2017-02-19 Thread Omar Sandoval
On Fri, Feb 17, 2017 at 04:43:56PM -0800, James Bottomley wrote: > This seems to be related to a 0day test we got on the block tree, > details here: > > http://marc.info/?t=14862406881 > > I root caused the above to something not being released when it should > be, so it looks like you have

Re: Manual driver binding and unbinding broken for SCSI

2017-02-17 Thread James Bottomley
On Fri, 2017-02-17 at 16:30 -0800, Omar Sandoval wrote: > Hi, everyone, > > As per $SUBJECT, I can cause a crash on v4.10-rc8, Jens' block/for > -next, > and Jan's bdi branch [1] by doing this: > > # lsscsi > [0:0:0:0]diskQEMU QEMU HARDDISK2.5+ /dev/sda > # echo 0:0:0:0 >

Manual driver binding and unbinding broken for SCSI

2017-02-17 Thread Omar Sandoval
Hi, everyone, As per $SUBJECT, I can cause a crash on v4.10-rc8, Jens' block/for-next, and Jan's bdi branch [1] by doing this: # lsscsi [0:0:0:0]diskQEMU QEMU HARDDISK2.5+ /dev/sda # echo 0:0:0:0 > /sys/bus/scsi/drivers/sd/unbind # echo 0:0:0:0 > /sys/bus/scsi/drivers/sd/bind