search for: iov_iter_get_pages_alloc

...virtio: fix error handling for debug builds Minfei Huang (1): virtio_blk: Fix a slient kernel panic Stefan Hajnoczi (2): vhost/vsock: fix vhost virtio_vsock_pkt use-after-free virtio-vsock: fix include guard typo Vegard Nossum (1): 9p/trans_virtio: use kvfree() for iov_iter_get_pages_alloc() Wei Yongjun (1): virtio: fix memory leak in virtqueue_add() include/uapi/linux/virtio_vsock.h | 2 +- drivers/block/virtio_blk.c | 26 ++++++++------------------ drivers/s390/virtio/kvm_virtio.c | 4 +++- drivers/vhost/vsock.c | 6 +++++- drivers/virtio/virtio_ring...

...of those ITER_BVEC needs a user page reference, so we want to call put_user_page* on it. ITER_BVEC always already has page reference, which means in the block direct I/O path path we alread don't take a page reference. We should extent that handling to all other calls of iov_iter_get_pages / iov_iter_get_pages_alloc. I think we should just reject ITER_KVEC for direct I/O as well as we have no users and it is rather pointless. Alternatively if we see a use for it the callers should always have a life page reference anyway (or might be on kmalloc memory), so we really should not take a reference either. In ot...

...virtio: fix error handling for debug builds Minfei Huang (1): virtio_blk: Fix a slient kernel panic Stefan Hajnoczi (2): vhost/vsock: fix vhost virtio_vsock_pkt use-after-free virtio-vsock: fix include guard typo Vegard Nossum (1): 9p/trans_virtio: use kvfree() for iov_iter_get_pages_alloc() Wei Yongjun (1): virtio: fix memory leak in virtqueue_add() include/uapi/linux/virtio_vsock.h | 2 +- drivers/block/virtio_blk.c | 26 ++++++++------------------ drivers/s390/virtio/kvm_virtio.c | 4 +++- drivers/vhost/vsock.c | 6 +++++- drivers/virtio/virtio_ring...

...needs a user page reference, so we want to call > put_user_page* on it. ITER_BVEC always already has page reference, > which means in the block direct I/O path path we alread don't take > a page reference. We should extent that handling to all other calls > of iov_iter_get_pages / iov_iter_get_pages_alloc. I think we should > just reject ITER_KVEC for direct I/O as well as we have no users and > it is rather pointless. Alternatively if we see a use for it the > callers should always have a life page reference anyway (or might > be on kmalloc memory), so we really should not take a refe...

...needs a user page reference, so we want to call > put_user_page* on it. ITER_BVEC always already has page reference, > which means in the block direct I/O path path we alread don't take > a page reference. We should extent that handling to all other calls > of iov_iter_get_pages / iov_iter_get_pages_alloc. I think we should > just reject ITER_KVEC for direct I/O as well as we have no users and > it is rather pointless. Alternatively if we see a use for it the > callers should always have a life page reference anyway (or might > be on kmalloc memory), so we really should not take a refe...

From: John Hubbard <jhubbard at nvidia.com> Hi, This is mostly Jerome's work, converting the block/bio and related areas to call put_user_page*() instead of put_page(). Because I've changed Jerome's patches, in some cases significantly, I'd like to get his feedback before we actually leave him listed as the author (he might want to disown some or all of these). I added a

From: John Hubbard <jhubbard at nvidia.com> Hi, This is mostly Jerome's work, converting the block/bio and related areas to call put_user_page*() instead of put_page(). Because I've changed Jerome's patches, in some cases significantly, I'd like to get his feedback before we actually leave him listed as the author (he might want to disown some or all of these). I added a