From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Mark Amirkan via B4 Relay
<devnull+markdamirkan.gmail.com@kernel.org>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
netdev@vger.kernel.org
Cc: Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Jon Rosen <jrosen@cisco.com>, Simon Horman <horms@kernel.org>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net] net/packet: clear RX owner on VNET header error
Date: Sun, 13 Sep 2026 18:38:37 -0400 [thread overview]
Message-ID: <willemdebruijn.kernel.34fbab8b5c5af@gmail.com> (raw)
In-Reply-To: <20260913-b4-send-packet-vnet-v1-1-5545ffb528ae@gmail.com>
Mark Amirkan via B4 Relay wrote:
> From: Mark Amirkan <markdamirkan@gmail.com>
>
> Commit 61fad6816fc1 ("net/packet: tpacket_rcv: avoid a producer race
> condition") added rx_owner_map and made tpacket_rcv() claim a V1 or V2
> ring slot before converting the virtio-net header. If the conversion
> fails, the drop path leaves the slot claimed.
>
> With a one-frame TPACKET_V2 ring, an unsupported UDP GSO packet leaves
> the only slot unavailable, so the ring also drops the next valid packet.
>
> Clear the ownership bit on this error path. TPACKET_V3 already clears
> its block state here.
>
> Fixes: 61fad6816fc1 ("net/packet: tpacket_rcv: avoid a producer race condition")
> Cc: stable@vger.kernel.org
> Assisted-by: Symbolic
> Signed-off-by: Mark Amirkan <markdamirkan@gmail.com>
Reviewed-by: Willem de Bruijn <willemb@google.com>
prev parent reply other threads:[~2026-09-13 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 10:28 [PATCH net] net/packet: clear RX owner on VNET header error Mark Amirkan via B4 Relay
2026-09-13 22:38 ` Willem de Bruijn [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=willemdebruijn.kernel.34fbab8b5c5af@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=devnull+markdamirkan.gmail.com@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jrosen@cisco.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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