From: Arseniy Krasnov <avkrasnov@salutedevices.com>
To: Stefan Hajnoczi <stefanha@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Bobby Eshleman <bobby.eshleman@bytedance.com>
Cc: <kvm@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel@sberdevices.ru>, <oxffffaa@gmail.com>,
<avkrasnov@salutedevices.com>
Subject: [PATCH net-next v2 02/12] vsock: read from socket's error queue
Date: Sun, 1 Oct 2023 00:02:58 +0300 [thread overview]
Message-ID: <20230930210308.2394919-3-avkrasnov@salutedevices.com> (raw)
In-Reply-To: <20230930210308.2394919-1-avkrasnov@salutedevices.com>
This adds handling of MSG_ERRQUEUE input flag in receive call. This flag
is used to read socket's error queue instead of data queue. Possible
scenario of error queue usage is receiving completions for transmission
with MSG_ZEROCOPY flag. This patch also adds new defines: 'SOL_VSOCK'
and 'VSOCK_RECVERR'.
Signed-off-by: Arseniy Krasnov <avkrasnov@salutedevices.com>
---
Changelog:
v1 -> v2:
* Place new defines for userspace to the existing file 'vm_sockets.h'
instead of creating new one.
include/linux/socket.h | 1 +
include/uapi/linux/vm_sockets.h | 4 ++++
net/vmw_vsock/af_vsock.c | 6 ++++++
3 files changed, 11 insertions(+)
diff --git a/include/linux/socket.h b/include/linux/socket.h
index 39b74d83c7c4..cfcb7e2c3813 100644
--- a/include/linux/socket.h
+++ b/include/linux/socket.h
@@ -383,6 +383,7 @@ struct ucred {
#define SOL_MPTCP 284
#define SOL_MCTP 285
#define SOL_SMC 286
+#define SOL_VSOCK 287
/* IPX options */
#define IPX_TYPE 1
diff --git a/include/uapi/linux/vm_sockets.h b/include/uapi/linux/vm_sockets.h
index c60ca33eac59..b1a66c1a7054 100644
--- a/include/uapi/linux/vm_sockets.h
+++ b/include/uapi/linux/vm_sockets.h
@@ -191,4 +191,8 @@ struct sockaddr_vm {
#define IOCTL_VM_SOCKETS_GET_LOCAL_CID _IO(7, 0xb9)
+#define SOL_VSOCK 287
+
+#define VSOCK_RECVERR 1
+
#endif /* _UAPI_VM_SOCKETS_H */
diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
index d841f4de33b0..0365382beab6 100644
--- a/net/vmw_vsock/af_vsock.c
+++ b/net/vmw_vsock/af_vsock.c
@@ -110,6 +110,8 @@
#include <linux/workqueue.h>
#include <net/sock.h>
#include <net/af_vsock.h>
+#include <linux/errqueue.h>
+#include <uapi/linux/vm_sockets.h>
static int __vsock_bind(struct sock *sk, struct sockaddr_vm *addr);
static void vsock_sk_destruct(struct sock *sk);
@@ -2137,6 +2139,10 @@ vsock_connectible_recvmsg(struct socket *sock, struct msghdr *msg, size_t len,
int err;
sk = sock->sk;
+
+ if (unlikely(flags & MSG_ERRQUEUE))
+ return sock_recv_errqueue(sk, msg, len, SOL_VSOCK, VSOCK_RECVERR);
+
vsk = vsock_sk(sk);
err = 0;
--
2.25.1
next prev parent reply other threads:[~2023-09-30 21:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 21:02 [PATCH net-next v2 00/12] vsock/virtio: continue MSG_ZEROCOPY support Arseniy Krasnov
2023-09-30 21:02 ` [PATCH net-next v2 01/12] vsock: set EPOLLERR on non-empty error queue Arseniy Krasnov
2023-10-03 16:22 ` Stefano Garzarella
2023-09-30 21:02 ` Arseniy Krasnov [this message]
2023-10-03 16:23 ` [PATCH net-next v2 02/12] vsock: read from socket's " Stefano Garzarella
2023-09-30 21:02 ` [PATCH net-next v2 03/12] vsock: check for MSG_ZEROCOPY support on send Arseniy Krasnov
2023-09-30 21:03 ` [PATCH net-next v2 04/12] vsock: enable SOCK_SUPPORT_ZC bit Arseniy Krasnov
2023-09-30 21:03 ` [PATCH net-next v2 05/12] vhost/vsock: support MSG_ZEROCOPY for transport Arseniy Krasnov
2023-09-30 21:03 ` [PATCH net-next v2 06/12] vsock/virtio: " Arseniy Krasnov
2023-09-30 21:03 ` [PATCH net-next v2 07/12] vsock/loopback: " Arseniy Krasnov
2023-09-30 21:03 ` [PATCH net-next v2 08/12] vsock: enable setting SO_ZEROCOPY Arseniy Krasnov
2023-10-03 16:23 ` Stefano Garzarella
2023-09-30 21:03 ` [PATCH net-next v2 09/12] docs: net: description of MSG_ZEROCOPY for AF_VSOCK Arseniy Krasnov
2023-10-03 16:23 ` Stefano Garzarella
2023-09-30 21:03 ` [PATCH net-next v2 10/12] test/vsock: MSG_ZEROCOPY flag tests Arseniy Krasnov
2023-10-03 16:24 ` Stefano Garzarella
2023-10-04 5:24 ` Arseniy Krasnov
2023-10-04 15:39 ` Stefano Garzarella
2023-10-04 16:20 ` Arseniy Krasnov
2023-09-30 21:03 ` [PATCH net-next v2 11/12] test/vsock: MSG_ZEROCOPY support for vsock_perf Arseniy Krasnov
2023-10-04 15:45 ` Stefano Garzarella
2023-09-30 21:03 ` [PATCH net-next v2 12/12] test/vsock: io_uring rx/tx tests Arseniy Krasnov
2023-10-04 15:48 ` Stefano Garzarella
2023-10-03 16:26 ` [PATCH net-next v2 00/12] vsock/virtio: continue MSG_ZEROCOPY support Stefano Garzarella
2023-10-04 5:25 ` Arseniy Krasnov
2023-10-04 16:22 ` Arseniy Krasnov
2023-10-04 16:42 ` Stefano Garzarella
2023-10-04 16:40 ` Arseniy Krasnov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230930210308.2394919-3-avkrasnov@salutedevices.com \
--to=avkrasnov@salutedevices.com \
--cc=bobby.eshleman@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kernel@sberdevices.ru \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®