aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/greybus
diff options
context:
space:
mode:
authorJorgen Hansen <jhansen@vmware.com>2021-01-20 08:33:40 -0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-01-26 19:18:50 +0100
commit7eecea89e44f64e60f1410483e79a0cab18ad580 (patch)
tree0f27a2c7e71a620d9ba2f858454fb9126a301aec /drivers/greybus
parentVMCI: Use set_page_dirty_lock() when unregistering guest memory (diff)
downloadlinux-dev-7eecea89e44f64e60f1410483e79a0cab18ad580.tar.xz
linux-dev-7eecea89e44f64e60f1410483e79a0cab18ad580.zip
VMCI: Enforce queuepair max size for IOCTL_VMCI_QUEUEPAIR_ALLOC
When create the VMCI queue pair tracking data structures on the host side, the IOCTL for creating the VMCI queue pair didn't validate the queue pair size parameters. This change adds checks for this. This avoids a memory allocation issue in qp_host_alloc_queue, as reported by nslusarek@gmx.net. The check in qp_host_alloc_queue has also been updated to enforce the maximum queue pair size as defined by VMCI_MAX_GUEST_QP_MEMORY. The fix has been verified using sample code supplied by nslusarek@gmx.net. Reported-by: nslusarek@gmx.net Reviewed-by: Vishnu Dasa <vdasa@vmware.com> Signed-off-by: Jorgen Hansen <jhansen@vmware.com> Link: https://lore.kernel.org/r/1611160420-30573-1-git-send-email-jhansen@vmware.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/greybus')
0 files changed, 0 insertions, 0 deletions