Stefano Garzarella ebdede644b libvhost-user: mask F_INFLIGHT_SHMFD if memfd is not supported ... libvhost-user will panic when receiving VHOST_USER_GET_INFLIGHT_FD message if MFD_ALLOW_SEALING is not defined, since it's not able to create a memfd. VHOST_USER_GET_INFLIGHT_FD is used only if VHOST_USER_PROTOCOL_F_INFLIGHT_SHMFD is negotiated. So, let's mask that feature if the backend is not able to properly handle these messages. Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org> Tested-by: Philippe Mathieu-Daudé <philmd@linaro.org> Acked-by: Stefan Hajnoczi <stefanha@redhat.com> Reviewed-by: David Hildenbrand <david@redhat.com> Signed-off-by: Stefano Garzarella <sgarzare@redhat.com> Message-Id: <20240618100043.144657-5-sgarzare@redhat.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>		2024-07-02 09:27:56 -04:00
..
include
standard-headers
libvhost-user-glib.c
libvhost-user-glib.h
libvhost-user.c	libvhost-user: mask F_INFLIGHT_SHMFD if memfd is not supported	2024-07-02 09:27:56 -04:00
libvhost-user.h	libvhost-user: Bump up VHOST_USER_MAX_RAM_SLOTS to 509	2024-03-12 17:56:55 -04:00
link-test.c
meson.build