From mboxrd@z Thu Jan 1 00:00:00 1970 From: Omar Sandoval Subject: Re: Manual driver binding and unbinding broken for SCSI Date: Sun, 19 Feb 2017 18:19:58 -0800 Message-ID: <20170220021958.GA26238@vader> References: <20170218003015.GA19776@vader.DHCP.thefacebook.com> <1487378636.4351.45.camel@HansenPartnership.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1487378636.4351.45.camel@HansenPartnership.com> Sender: linux-block-owner@vger.kernel.org To: James Bottomley Cc: Dan Williams , Jan Kara , "Martin K. Petersen" , Jens Axboe , linux-scsi@vger.kernel.org, linux-block@vger.kernel.org List-Id: linux-scsi@vger.kernel.org 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=148624068800001 > > I root caused the above to something not being released when it should > be, so it looks like you have the same problem. It seems to be a > recent commit in the block tree, so could you bisect it since you have > a nice reproducer? These appear to actually be two separate issues. The unbind followed by bind crash only happens with scsi-mq. It reproes since at least 4.0. The unbind followed by a new device coming up crash happens both with and without scsi-mq. The earliest version I was able to check for that was 4.6, which did reproduce. I'll see if I can get some more info on these two issues separately.