From: patchwork-bot+netdevbpf@kernel.org
To: Michal Luczaj <mhal@rbox.co>
Cc: sgarzare@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
avkrasnov@salutedevices.com, virtualization@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] vsock: Fix SO_ZEROCOPY on accept()ed vsocks
Date: Tue, 06 Jan 2026 00:20:08 +0000 [thread overview]
Message-ID: <176765880886.1339098.1816013427410821419.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251229-vsock-child-sock-custom-sockopt-v2-0-64778d6c4f88@rbox.co>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 29 Dec 2025 20:43:09 +0100 you wrote:
> vsock has its own handling of setsockopt(SO_ZEROCOPY). Which works just
> fine unless socket comes from a call to accept(). Because
> SOCK_CUSTOM_SOCKOPT flag is missing, attempting to set the option always
> results in errno EOPNOTSUPP.
>
> Signed-off-by: Michal Luczaj <mhal@rbox.co>
>
> [...]
Here is the summary with links:
- [net,v2,1/2] vsock: Make accept()ed sockets use custom setsockopt()
https://git.kernel.org/netdev/net/c/ce5e612dd411
- [net,v2,2/2] vsock/test: Test setting SO_ZEROCOPY on accept()ed socket
https://git.kernel.org/netdev/net/c/caa20e9e155b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-06 0:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 19:43 Michal Luczaj
2025-12-29 19:43 ` [PATCH net v2 1/2] vsock: Make accept()ed sockets use custom setsockopt() Michal Luczaj
2025-12-29 19:43 ` [PATCH net v2 2/2] vsock/test: Test setting SO_ZEROCOPY on accept()ed socket Michal Luczaj
2026-01-06 0:20 ` patchwork-bot+netdevbpf [this message]
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=176765880886.1339098.1816013427410821419.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=avkrasnov@salutedevices.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhal@rbox.co \
--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
all inboxes | Powered by JetHome®