Displaying 3 results from an estimated 3 matches for "scsi_common".
Did you mean:
scsi_command
2023 Mar 05
1
ocfs2 xattr
...ore configfs qemu_fw_cfg ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic hid_generic usbhid hid xhci_pci xhci_hcd ahci libahci libata virtio_net net_failover virtio_blk failover usbcore scsi_mod psmouse crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel i2c_i801 i2c_smbus scsi_common
[ 27.392203] lpc_ich virtio_pci virtio_pci_legacy_dev virtio_pci_modern_dev usb_common virtio virtio_ring
[ 27.396539] CR2: 0000000000000000
[ 27.397026] ---[ end trace 0000000000000000 ]---
[ 27.397518] RIP: 0010:strlen+0x0/0x20
[ 27.398009] Code: b6 07 38 d0 74 14 48 83 c7 01 84 c0 74...
2023 Jul 09
4
[PATCH v2 0/2] vhost-scsi: Fix IO hangs when using windows
The following patches were made over Linus's tree and fix an issue
where windows guests will send iovecs with offset/lengths that result
in IOs that are not aligned to 512. The LIO layer will then send them
to Linux's FS/block layer but it requires 512 byte alignment, so
depending on the FS/block driver being used we will get IO errors or
hung IO.
The following patches have vhost-scsi
2023 May 24
4
[PATCH 0/3] vhost-scsi: Fix IO hangs when using windows
The following patches were made over Linus's tree and fix an issue
where windows guests will send iovecs with offset/lengths that result
in IOs that are not aligned to 512. The LIO layer will then send them
to Linux's block layer but it requires 512 byte alignment, so depending
on the block driver being used we will get IO errors or hung IO.
The following patches have vhost-scsi detect