On Wed, Feb 10, 2016 at 07:34:51AM -0800, James Bottomley wrote: > On Wed, 2016-02-10 at 15:05 +0100, Johannes Thumshirn wrote: > > On Wed, Feb 03, 2016 at 11:38:16PM +0100, Sebastian Herbszt wrote: > > > James Bottomley wrote: > > > > On Mon, 2016-02-01 at 19:43 -0800, Bart Van Assche wrote: > > > > > On 01/19/16 17:03, James Bottomley wrote: > > > > > > On Tue, 2016-01-19 at 19:30 -0500, Martin K. Petersen wrote: > > > > > > > > > > > > "Bart" == Bart Van Assche < > > > > > > > > > > > > bart.vanassche@xxxxxxxxxxx> [..] > > > > > > Sebastian > > > > Hi James, Bart, Martin > > > > Have you already decided, which of the two patches you favour and > > when it'llbe included? > > > > I have several customer reports that hit this lockup and I don't want > > to include one of the patches from the list just to find out the > > other one's is used in mainline. > > Well, unless the target allocation bug gets fixed in Bart's, it will > have to be the last_scan one. It's more a hack than a fix, but I > suppose it will do as a bandaid in the meantime. > > If you have diagnosed this at customers, I'd still like to know what's > holding the devices on removal. > > Thanks, > > James I'll setup a test environment tomorrow and try to get some crash dumps with the current HEAD. -- Johannes Thumshirn Storage jthumshirn@xxxxxxx +49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850 -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
