From: sashiko-bot@kernel.org
To: physicalmtea@gmail.com
Cc: virtualization@lists.linux.dev,
"Michael S. Tsirkin" <mst@redhat.com>,
kvm@vger.kernel.org, "Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH 1/5] vsock: split socket lookup from locked RX processing
Date: Sat, 03 Oct 2026 07:46:53 +0000 [thread overview]
Message-ID: <20261003074654.579841F0089B@smtp.kernel.org> (raw)
In-Reply-To: <20261002074551.318789-2-physicalmtea@gmail.com>
> From: Jia Jia <physicalmtea@gmail.com>
>
> Split virtio_transport_recv_pkt() so socket lookup is separate from the
> receive state machine that runs under the socket lock.
>
> Keep virtio_transport_recv_pkt() on its existing per-packet locking path.
> Pass the source and destination addresses used for lookup to the locked
> receive path so they are decoded only once.
>
> Pass the network namespace and decoded address tuple to the locked receive
> path through a packet context so later extensions remain cleanly
> encapsulated.
>
> Preserve source validation and failure handling. Keep the lookup reference
> separate from the skb owner reference so a later patch can retain it while
> processing a bounded run of packets under one socket lock.
>
> Signed-off-by: Jia Jia <physicalmtea@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261002074551.318789-1-physicalmtea@gmail.com?part=1
next prev parent reply other threads:[~2026-10-03 7:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 7:45 [PATCH 1/5] vsock: split socket lookup from locked RX processing physicalmtea
2026-10-03 7:46 ` sashiko-bot [this message]
2026-10-08 17:03 ` Jakub Kicinski
2026-10-08 17:04 ` Jakub Kicinski
2026-10-09 1:59 ` Jia Jia
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=20261003074654.579841F0089B@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eperezma@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=physicalmtea@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
--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