On Fri, 2014-05-02 at 12:26 -0700, Dan Williams wrote: > On Fri, May 2, 2014 at 12:01 PM, Joe Lawrence <joe.lawrence@xxxxxxxxxxx> wrote: > > On Wed, 2 Apr 2014 16:48:52 -0400 > > Joe Lawrence <joe.lawrence@xxxxxxxxxxx> wrote: > > > >> On Wed, 2 Apr 2014 16:40:41 -0400 > >> Joe Lawrence <joe.lawrence@xxxxxxxxxxx> wrote: > >> > >> > Since bsg creation is a side effect of sas_rphy_add, move its > >> > complementary removal call into sas_rphy_remove. > >> > >> Hello James, > >> > >> This a resend of a patch posted to quiet an end-device sysfs warning in > >> its device deletion path when removing the mpt2sas driver: > >> > >> (initial report) > >> sysfs group not found for kobject on mpt2sas unload > >> http://marc.info/?t=138497460000004 > >> > >> (patch + ACK + comments) > >> http://marc.info/?t=138609455500001 > >> > >> (gentoo, LSI repro) > >> mpt2sas driver barfs when force removing a drive on 3.13.1 > >> http://marc.info/?t=139122351300001 > >> > >> Dan Williams had a few other suggestions for cleanup in this area, but > >> those could be handled in a subsequent patch. This one missed 3.14 > >> inclusion and the warning still occurs in Linus's tree as of today > >> (post scsi/block merge) hence the repost. > > > > Ping? Just reproduced on 3.15-rc3. Also found this: > > > > (~500 repro count on Fedora Problem Tracker) > > http://retrace.fedoraproject.org/faf/problems/1623421/ > > > > Hmm, looks like the re-send is missing my ack. Feel free to add: > > Acked-by: Dan Williams <dan.j.williams@xxxxxxxxx> > > James, do you want me to shepherd sas infrastructure bits > (libsas/scsi_transport_sas) along in my own tree, or...? Well, let's try a tree for enhancements ... you know the drill: signed pull to me on or before -rc6. This one, based on the fedora tracker info (only just shown) looks like a bug affecting older kernels, so necessitating a cc to stable, right? I'll take it through scsi-fixes James -- 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
