search for: noident

Hi: This series tries to fix various issues of vhost: - Patch 1 adds a missing write barrier between used idx updating and logging. - Patch 2-3 brings back the protection of device IOTLB through vq mutex, this fixes possible use after free in device IOTLB entries. - Patch 4 fixes the diry page logging when device IOTLB is enabled. We should done through GPA instead of GIOVA, this was done

Hi: This series tries to fix various issues of vhost: - Patch 1 adds a missing write barrier between used idx updating and logging. - Patch 2-3 brings back the protection of device IOTLB through vq mutex, this fixes possible use after free in device IOTLB entries. - Patch 4 fixes the diry page logging when device IOTLB is enabled. We should done through GPA instead of GIOVA, this was done

...virtio/virtio_pci_modern.c:150:32: warning: incorrect type in argument 2 (different base types) drivers/virtio/virtio_pci_modern.c:150:32: expected unsigned int [noderef] [usertype] <asn:2>*addr drivers/virtio/virtio_pci_modern.c:150:32: got restricted __le32 [noderef] <asn:2>*<noident> drivers/virtio/virtio_pci_modern.c:151:39: warning: incorrect type in argument 1 (different base types) drivers/virtio/virtio_pci_modern.c:151:39: expected unsigned int [noderef] [usertype] <asn:2>*addr drivers/virtio/virtio_pci_modern.c:151:39: got restricted __le32 [noderef] <a...

...4 drivers/firmware/qemu_fw_cfg.c:131:27: sparse: incorrect type in initializer (different base types) @@ expected unsigned int length @@ got ed int length @@ drivers/firmware/qemu_fw_cfg.c:131:27: expected unsigned int length drivers/firmware/qemu_fw_cfg.c:131:27: got restricted __be32 <noident> drivers/firmware/qemu_fw_cfg.c:132:28: sparse: incorrect type in initializer (different base types) @@ expected unsigned int control @@ got ed int control @@ drivers/firmware/qemu_fw_cfg.c:132:28: expected unsigned int control drivers/firmware/qemu_fw_cfg.c:132:28: got restricted __be3...

I found some warnings reported by sparse in the virtio code when I checked virtio-crypto's driver stuff. Let's fix them. Gonglei (2): virtio_pci_modern: fix complaint by sparse virtio_ring: fix complaint by sparse drivers/virtio/virtio_pci_modern.c | 8 ++++---- drivers/virtio/virtio_ring.c | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) -- 1.8.3.1

I found some warnings reported by sparse in the virtio code when I checked virtio-crypto's driver stuff. Let's fix them. Gonglei (2): virtio_pci_modern: fix complaint by sparse virtio_ring: fix complaint by sparse drivers/virtio/virtio_pci_modern.c | 8 ++++---- drivers/virtio/virtio_ring.c | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) -- 1.8.3.1

When we use this pointer, we cast away the const modifier and modify the data. I think it was an accident to declare it as const. Signed-off-by: Dan Carpenter <dan.carpenter at oracle.com> diff --git a/include/xen/privcmd.h b/include/xen/privcmd.h index a853168..58ed953 100644 --- a/include/xen/privcmd.h +++ b/include/xen/privcmd.h @@ -69,7 +69,7 @@ struct privcmd_mmapbatch_v2 {

When we use this pointer, we cast away the const modifier and modify the data. I think it was an accident to declare it as const. Signed-off-by: Dan Carpenter <dan.carpenter at oracle.com> diff --git a/include/xen/privcmd.h b/include/xen/privcmd.h index a853168..58ed953 100644 --- a/include/xen/privcmd.h +++ b/include/xen/privcmd.h @@ -69,7 +69,7 @@ struct privcmd_mmapbatch_v2 {

...r # #imap4 stream tcp nowait root /usr/local/libexec/imapd imapd # # Return error for all "ident" requests # #auth stream tcp nowait root internal #auth stream tcp6 nowait root internal # # Provide internally a real "ident" service which provides ~/.fakeid support, # provides ~/.noident support, reports UNKNOWN as the operating system type # and times out after 30 seconds. # #auth stream tcp nowait root internal auth -r -f -n -o UNKNOWN -t 30 #auth stream tcp6 nowait root internal auth -r -f -n -o UNKNOWN -t 30 # # Example entry for an external ident server # #auth stream tcp wait...

Hi Alasdair, This is dm-ioband v1.12.2 release that is a minor update to fit the current dm-devel tree. Could you please replace dm-add-ioband.patch in your tree with this patch? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to upstream. Thanks, Ryo Tsuruta About dm-ioband: dm-ioband is an I/O bandwidth controller implemented as a device-mapper

Hi Alasdair, This is dm-ioband v1.12.2 release that is a minor update to fit the current dm-devel tree. Could you please replace dm-add-ioband.patch in your tree with this patch? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to upstream. Thanks, Ryo Tsuruta About dm-ioband: dm-ioband is an I/O bandwidth controller implemented as a device-mapper

Hi Alasdair, This is dm-ioband v1.12.2 release that is a minor update to fit the current dm-devel tree. Could you please replace dm-add-ioband.patch in your tree with this patch? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to upstream. Thanks, Ryo Tsuruta About dm-ioband: dm-ioband is an I/O bandwidth controller implemented as a device-mapper

Hi gang, I was a little surprised to see that patch go by recently which fixed an endian bug. I went to see how sparse checking looked and it was.. broken. I got it going again in my Fedora environment. Most of the patches are just cleanups, but there *were* three real bugs lurking in all that sparse warning spam. So I maintain that it''s worth our time to keep it going and fix