search for: config_virtio_blk_scsi

...------ 3 files changed, 1 insertion(+), 125 deletions(-) diff --git a/arch/powerpc/configs/guest.config b/arch/powerpc/configs/guest.config index 8b8cd18ecd7c..209f58515d88 100644 --- a/arch/powerpc/configs/guest.config +++ b/arch/powerpc/configs/guest.config @@ -1,5 +1,4 @@ CONFIG_VIRTIO_BLK=y -CONFIG_VIRTIO_BLK_SCSI=y CONFIG_SCSI_VIRTIO=y CONFIG_VIRTIO_NET=y CONFIG_NET_FAILOVER=y diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig index 1bb8ec575352..025b1b77b11a 100644 --- a/drivers/block/Kconfig +++ b/drivers/block/Kconfig @@ -432,16 +432,6 @@ config VIRTIO_BLK This is the virtual block driver...

...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

...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 Wed, Dec 11, 2019 at 09:42:49PM +0100, Arnd Bergmann wrote: > Each driver calling scsi_ioctl() gets an equivalent compat_ioctl() > handler that implements the same commands by calling scsi_compat_ioctl(). > > The scsi_cmd_ioctl() and scsi_cmd_blk_ioctl() functions are compatible > at this point, so any driver that calls those can do so for both native > and compat mode, with

On Wed, Dec 11, 2019 at 09:42:49PM +0100, Arnd Bergmann wrote: > Each driver calling scsi_ioctl() gets an equivalent compat_ioctl() > handler that implements the same commands by calling scsi_compat_ioctl(). > > The scsi_cmd_ioctl() and scsi_cmd_blk_ioctl() functions are compatible > at this point, so any driver that calls those can do so for both native > and compat mode, with

On Thu, Dec 12, 2019 at 01:28:08AM +0100, Paolo Bonzini wrote: > I think it's because the only ioctl for virtio-blk is SG_IO. It makes > sense to lump it in with scsi, but I wouldn't mind getting rid of > CONFIG_VIRTIO_BLK_SCSI altogether. CONFIG_VIRTIO_BLK_SCSI has been broken for about two years, as it never set the QUEUE_FLAG_SCSI_PASSTHROUGH flag after that was introduced. I actually have a patch that I plan to send to remove this support as it was a really idea to start with (speaking as the person who had that ide...

Hi, Fedora got a bug report on an early version of 4.13.2 https://paste.fedoraproject.org/paste/t-Yx23LN5QwJ7oPZLj3zrg [ 5.913866] usercopy: kernel memory overwrite attempt detected to (null) (<null>) (16 bytes) [ 5.914199] ------------[ cut here ]------------ [ 5.914201] kernel BUG at mm/usercopy.c:72! [ 5.914279] invalid opcode: 0000 [#1] SMP [ 5.914293] Modules

Hi, Fedora got a bug report on an early version of 4.13.2 https://paste.fedoraproject.org/paste/t-Yx23LN5QwJ7oPZLj3zrg [ 5.913866] usercopy: kernel memory overwrite attempt detected to (null) (<null>) (16 bytes) [ 5.914199] ------------[ cut here ]------------ [ 5.914201] kernel BUG at mm/usercopy.c:72! [ 5.914279] invalid opcode: 0000 [#1] SMP [ 5.914293] Modules

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...

...8 @@ static int virtblk_map_queues(struct blk_mq_tag_set *set) { struct virtio_blk *vblk = set->driver_data; - return blk_mq_virtio_map_queues(&set->map[0], vblk->vdev, 0); + return blk_mq_virtio_map_queues(&set->map[HCTX_TYPE_DEFAULT], + vblk->vdev, 0); } #ifdef CONFIG_VIRTIO_BLK_SCSI -- 2.7.4

Hi all, this series builds on my previous changes in Jens' for-4.11/rq-refactor branch that split out the BLOCK_PC fields from struct request into a new struct scsi_request, and makes support for struct scsi_request and the SCSI passthrough ioctls optional. It is now only enabled by drivers that need it. In addition I've made SCSI passthrough support in the virtio_blk driver an optional

Hi all, this series builds on my previous changes in Jens' for-4.11/rq-refactor branch that split out the BLOCK_PC fields from struct request into a new struct scsi_request, and makes support for struct scsi_request and the SCSI passthrough ioctls optional. It is now only enabled by drivers that need it. In addition I've made SCSI passthrough support in the virtio_blk driver an optional

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?

...if >> .owner = THIS_MODULE, >> .getgeo = virtblk_getgeo, >> }; > Hmm - is virtio blk lumped in with scsi things intentionally? I think it's because the only ioctl for virtio-blk is SG_IO. It makes sense to lump it in with scsi, but I wouldn't mind getting rid of CONFIG_VIRTIO_BLK_SCSI altogether. Paolo

No need to get into the submenu to disable all VIRTIO-related config entries. This makes it easier to disable all VIRTIO config options without entering the submenu. It will also enable one to see that en/dis-abled state from the outside menu. This is only intended to change menuconfig UI, not change the config dependencies. Signed-off-by: Vincent Legoll <vincent.legoll at gmail.com> ---

No need to get into the submenu to disable all VIRTIO-related config entries. This makes it easier to disable all VIRTIO config options without entering the submenu. It will also enable one to see that en/dis-abled state from the outside menu. This is only intended to change menuconfig UI, not change the config dependencies. Signed-off-by: Vincent Legoll <vincent.legoll at gmail.com> ---

..._DRBD is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SKD is not set # CONFIG_BLK_DEV_SX8 is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_CDROM_PKTCDVD is not set # CONFIG_ATA_OVER_ETH is not set CONFIG_XEN_BLKDEV_FRONTEND=y # CONFIG_XEN_BLKDEV_BACKEND is not set CONFIG_VIRTIO_BLK=y CONFIG_VIRTIO_BLK_SCSI=y # CONFIG_BLK_DEV_RBD is not set # CONFIG_BLK_DEV_RSXX is not set # CONFIG_BLK_DEV_NVME is not set # CONFIG_NVME_FC is not set # # Misc devices # # CONFIG_SENSORS_LIS3LV02D is not set # CONFIG_AD525X_DPOT is not set # CONFIG_DUMMY_IRQ is not set # CONFIG_IBM_ASM is not set # CONFIG_PHANTOM is not...

..._DRBD is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SKD is not set # CONFIG_BLK_DEV_SX8 is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_CDROM_PKTCDVD is not set # CONFIG_ATA_OVER_ETH is not set CONFIG_XEN_BLKDEV_FRONTEND=y # CONFIG_XEN_BLKDEV_BACKEND is not set CONFIG_VIRTIO_BLK=y CONFIG_VIRTIO_BLK_SCSI=y # CONFIG_BLK_DEV_RBD is not set # CONFIG_BLK_DEV_RSXX is not set # CONFIG_BLK_DEV_NVME is not set # CONFIG_NVME_FC is not set # # Misc devices # # CONFIG_SENSORS_LIS3LV02D is not set # CONFIG_AD525X_DPOT is not set # CONFIG_DUMMY_IRQ is not set # CONFIG_IBM_ASM is not set # CONFIG_PHANTOM is not...

...set > # CONFIG_BLK_DEV_SKD is not set > # CONFIG_BLK_DEV_SX8 is not set > # CONFIG_BLK_DEV_RAM is not set > # CONFIG_CDROM_PKTCDVD is not set > # CONFIG_ATA_OVER_ETH is not set > CONFIG_XEN_BLKDEV_FRONTEND=y > # CONFIG_XEN_BLKDEV_BACKEND is not set > CONFIG_VIRTIO_BLK=y > CONFIG_VIRTIO_BLK_SCSI=y > # CONFIG_BLK_DEV_RBD is not set > # CONFIG_BLK_DEV_RSXX is not set > # CONFIG_BLK_DEV_NVME is not set > # CONFIG_NVME_FC is not set > > # > # Misc devices > # > # CONFIG_SENSORS_LIS3LV02D is not set > # CONFIG_AD525X_DPOT is not set > # CONFIG_DUMMY_IRQ is not...

..._DRBD is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SKD is not set # CONFIG_BLK_DEV_SX8 is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_CDROM_PKTCDVD is not set # CONFIG_ATA_OVER_ETH is not set CONFIG_XEN_BLKDEV_FRONTEND=y # CONFIG_XEN_BLKDEV_BACKEND is not set CONFIG_VIRTIO_BLK=y CONFIG_VIRTIO_BLK_SCSI=y # CONFIG_BLK_DEV_RBD is not set # CONFIG_BLK_DEV_RSXX is not set # # NVME Support # # CONFIG_BLK_DEV_NVME is not set # CONFIG_NVME_FC is not set # CONFIG_NVME_TARGET is not set # # Misc devices # # CONFIG_SENSORS_LIS3LV02D is not set # CONFIG_AD525X_DPOT is not set # CONFIG_DUMMY_IRQ is not set...