> On 10 Aug 2018, at 03:15, Greg Kroah-Hartman <gre...@linuxfoundation.org> > wrote: > > On Fri, Aug 10, 2018 at 10:31:29AM +0800, Ming Lei wrote: >> On Fri, Aug 10, 2018 at 02:09:01AM +0000, Felipe Franciosi wrote: >>> Hi Ming (and all), >>> >>> Your series "scsi: virtio_scsi: fix IO hang caused by irq vector automatic >>> affinity" which forces virtio-scsi to use blk-mq fixes an issue introduced >>> by 84676c1f. We noticed that this bug also exists in 4.14.y (as >>> ef86f3a72adb), but your series was not backported to that stable branch. >>> >>> Are there any plans to do that? At least CoreOS is using 4.14 and showing >>> issues on AHV (which provides an mq virtio-scsi controller). >>> >> >> Hi Felipe, >> >> Looks the following 4 patches should have been marked as stable, sorry >> for missing that. >> >> b5b6e8c8d3b4 scsi: virtio_scsi: fix IO hang caused by automatic irq vector >> affinity >> 2f31115e940c scsi: core: introduce force_blk_mq >> adbe552349f2 scsi: megaraid_sas: fix selection of reply queue >> 8b834bff1b73 scsi: hpsa: fix selection of reply queue >> >> Usually this backporting is done by our stable guys, so I will CC stable >> and leave them handle it, but I am happy to provide any help for >> addressing conflicts or sort of thing. > > As the above patches do not apply "cleanly" to the 4.14.y tree at all, > can you please provide a set of backported patches that I can apply?
Actually, adbe552349f2 is already present in 4.14.y. It is commit e58114824fa6. If you skip that, all the other three apply cleanly. Thanks, Felipe > > thanks, > > greg k-h
