From: patchwork-bot+netdevbpf@kernel.org
To: Daehyeon Ko <4ncienth@gmail.com>
Cc: netdev@vger.kernel.org, sgarzare@redhat.com, stefanha@redhat.com,
bobbyeshleman@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, mst@redhat.com, jasowangio@gmail.com,
xuanzhuo@linux.alibaba.com, eperezma@redhat.com,
bryan-bt.tan@broadcom.com, vishnu.dasa@broadcom.com,
bcm-kernel-feedback-list@broadcom.com,
virtualization@lists.linux.dev, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v4 0/2] vsock: validate packet sources after bound lookup fallback
Date: Tue, 01 Sep 2026 00:00:12 +0000 [thread overview]
Message-ID: <178822081213.841883.14927327834085182039.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260826003929.966160-1-4ncienth@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 26 Aug 2026 09:39:26 +0900 you wrote:
> Both virtio and VMCI look up connected sockets by the full tuple before
> falling back to a destination-only bound lookup. The fallback can select a
> non-listening socket without validating the packet source.
>
> V2 covered only the virtio path. Following Stefano's review, this series
> moves the source and transport validation into a documented AF_VSOCK helper
> and uses it for both virtio and VMCI. The VMCI patch checks both its
> bottom-half and deferred workqueue receive paths.
>
> [...]
Here is the summary with links:
- [net,v4,1/2] vsock/virtio: validate packet source for connected sockets
https://git.kernel.org/netdev/net/c/dee44f41f206
- [net,v4,2/2] vsock/vmci: validate packet source for connected sockets
https://git.kernel.org/netdev/net/c/ad9a7da3fa39
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-09-01 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 0:39 Daehyeon Ko
2026-08-26 0:39 ` [PATCH net v4 1/2] vsock/virtio: validate packet source for connected sockets Daehyeon Ko
2026-08-26 0:39 ` [PATCH net v4 2/2] vsock/vmci: " Daehyeon Ko
2026-08-31 22:33 ` Vishnu Dasa
2026-09-01 0:00 ` 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=178822081213.841883.14927327834085182039.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=4ncienth@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bobbyeshleman@gmail.com \
--cc=bryan-bt.tan@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=horms@kernel.org \
--cc=jasowangio@gmail.com \
--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=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=vishnu.dasa@broadcom.com \
--cc=xuanzhuo@linux.alibaba.com \
/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®