On 09/15/2017 10:37 AM, Christoph Hellwig wrote:> On Fri, Sep 15, 2017 at 09:54:08AM -0700, Laura Abbott wrote: >> Hi, >> >> Fedora got a bug report on an early version of 4.13.2 >> https://paste.fedoraproject.org/paste/t-Yx23LN5QwJ7oPZLj3zrg > > Can you check if the issue goes away when you disable > CONFIG_VIRTIO_BLK_SCSI? >Yes, the issue goes away when CONFIG_VIRTIO_BLK_SCSI is disabled. Thanks, Laura
On Sat, Sep 16, 2017 at 04:16:06PM -0700, Laura Abbott wrote:> Yes, the issue goes away when CONFIG_VIRTIO_BLK_SCSI is > disabled.Ok, so it's probably related to follow ups to the scsi_request split. That being said, I would highly recommend turning off CONFIG_VIRTIO_BLK_SCSI in fedora. The feature has caused more trouble than it helped with, and should never have been added (saying that as the person who added it). It was never supported with virtio 1.0 devices and has been disabled in qemu by default for quite a while.
On 09/17/2017 04:57 PM, Christoph Hellwig wrote:> On Sat, Sep 16, 2017 at 04:16:06PM -0700, Laura Abbott wrote: >> Yes, the issue goes away when CONFIG_VIRTIO_BLK_SCSI is >> disabled. > > Ok, so it's probably related to follow ups to the scsi_request split. > > That being said, I would highly recommend turning off > CONFIG_VIRTIO_BLK_SCSI in fedora. The feature has caused more trouble > than it helped with, and should never have been added (saying that as > the person who added it). It was never supported with virtio 1.0 devices > and has been disabled in qemu by default for quite a while. >Thanks for the pointer, I went and turned it off on our 4.13 based kernels. Laura