From: David Carlier <devnexen@gmail.com>
To: netdev@vger.kernel.org
Cc: sgarzare@redhat.com, bobbyeshleman@gmail.com,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
David Carlier <devnexen@gmail.com>
Subject: [PATCH net-next v3 0/3] vsock: SO_INQ for stream sockets
Date: Fri, 16 Oct 2026 14:27:13 +0100 [thread overview]
Message-ID: <20261016132716.272018-1-devnexen@gmail.com> (raw)
This is the follow-up announced in the receive queue hint series [1]:
SO_INQ and SCM_INQ for AF_VSOCK stream sockets, as AF_UNIX has.
Patch 1 moves the SOL_SOCKET option handling to a helper without
functional change, patch 2 adds SO_INQ and patch 3 covers it in
vsock_test.
The value is the one SIOCINQ returns, so on Hyper-V it covers the
current packet only. Accepted sockets inherit the flag from the
listener, and the sockmap receive path does not report it.
Tested over loopback with vsock_test and vsock_uring_test.
v3:
- split the SOL_SOCKET refactor out of the SO_INQ patch (Stefano)
- rename vsock_custom_sockopt() to vsock_sol_socket_custom() (Stefano)
- parse the value in vsock_sol_socket_get_bool() after the per option
checks, so SO_INQ on SOCK_SEQPACKET always fails with ENOPROTOOPT
(Stefano)
- reflow the comment to 80 columns (Stefano)
- carry Reviewed-by and Acked-by on the test patch; Bobby's Acked-by
on the v2 kernel patch is dropped since it was split and reworked
v2: https://lore.kernel.org/netdev/20261015154334.3217358-1-devnexen@gmail.com/
v1: https://lore.kernel.org/netdev/20261012235524.41468-1-devnexen@gmail.com/
[1] https://lore.kernel.org/netdev/20260923184008.153541-1-devnexen@gmail.com/
David Carlier (3):
vsock: move SOL_SOCKET options to vsock_sol_socket_setsockopt()
vsock: support SO_INQ on stream sockets
vsock/test: cover SO_INQ
include/net/af_vsock.h | 1 +
net/vmw_vsock/af_vsock.c | 125 ++++++++++----
tools/testing/vsock/vsock_test.c | 279 +++++++++++++++++++++++++++++++
3 files changed, 377 insertions(+), 28 deletions(-)
base-commit: a4057f51efc2b74ddf46721e83f45e9efb13649d
--
2.55.0
next reply other threads:[~2026-10-16 13:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 13:27 David Carlier [this message]
2026-10-16 13:27 ` [PATCH net-next v3 1/3] vsock: move SOL_SOCKET options to vsock_sol_socket_setsockopt() David Carlier
2026-10-16 13:27 ` [PATCH net-next v3 2/3] vsock: support SO_INQ on stream sockets David Carlier
2026-10-16 13:27 ` [PATCH net-next v3 3/3] vsock/test: cover SO_INQ David Carlier
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=20261016132716.272018-1-devnexen@gmail.com \
--to=devnexen@gmail.com \
--cc=bobbyeshleman@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux.dev \
/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