From: patchwork-bot+netdevbpf@kernel.org
To: Harshitha Ramamurthy <hramamurthy@google.com>
Cc: netdev@vger.kernel.org, joshwash@google.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, willemb@google.com,
pkaligineedi@google.com, linux-kernel@vger.kernel.org,
maxyuan@google.com, jordanrhee@google.com
Subject: Re: [PATCH net-next] gve: Fix race condition on tx->dropped_pkt update
Date: Fri, 28 Nov 2025 02:20:21 +0000 [thread overview]
Message-ID: <176429642154.114872.15685538167774885821.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251127000751.662959-1-hramamurthy@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 27 Nov 2025 00:07:51 +0000 you wrote:
> From: Max Yuan <maxyuan@google.com>
>
> The tx->dropped_pkt counter is a 64-bit integer that is incremented
> directly. On 32-bit architectures, this operation is not atomic and
> can lead to read/write tearing if a reader accesses the counter during
> the update. This can result in incorrect values being reported for
> dropped packets.
>
> [...]
Here is the summary with links:
- [net-next] gve: Fix race condition on tx->dropped_pkt update
https://git.kernel.org/netdev/net-next/c/858b1d07e491
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:[~2025-11-28 2:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 0:07 Harshitha Ramamurthy
2025-11-28 2: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=176429642154.114872.15685538167774885821.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=jordanrhee@google.com \
--cc=joshwash@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxyuan@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=willemb@google.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®