From: patchwork-bot+netdevbpf@kernel.org
To: <enrico.zanda@arm.com>
Cc: jasowangio@gmail.com, virtualization@lists.linux.dev,
mst@redhat.com, netdev@vger.kernel.org, kuba@kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
eperezma@redhat.com, nd@arm.com
Subject: Re: [PATCH net] vhost-net: fix TX stall when vhost owns virtio-net header
Date: Tue, 21 Jul 2026 13:20:06 +0000 [thread overview]
Message-ID: <178464000690.281806.12019184491759783883.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260708152242.2268848-1-enrico.zanda@arm.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 8 Jul 2026 16:22:42 +0100 you wrote:
> From: Enrico Zanda <enrico.zanda@arm.com>
>
> When vhost owns the virtio-net header, i.e. when
> VHOST_NET_F_VIRTIO_NET_HDR is negotiated, sock_hlen is 0,
> meaning that no header will be forwarded to the TAP device.
>
> In the current vhost_net_build_xdp() implementation,
> when sock_hlen == 0, the gso pointer can point at the start of the
> Ethernet frame instead of a virtio-net header.
> This results in a wrong interpretation of the destination MAC address
> bytes as struct virtio_net_hdr fields.
>
> [...]
Here is the summary with links:
- [net] vhost-net: fix TX stall when vhost owns virtio-net header
https://git.kernel.org/netdev/net/c/3c0d10f233f1
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-07-21 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 15:22 [PATCH net] vhost-net: fix TX stall when vhost owns virtio-net header enrico.zanda
2026-07-08 16:50 ` Michael S. Tsirkin
2026-07-21 11:19 ` Paolo Abeni
2026-07-21 13: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=178464000690.281806.12019184491759783883.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=enrico.zanda@arm.com \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=nd@arm.com \
--cc=netdev@vger.kernel.org \
--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