From: patchwork-bot+netdevbpf@kernel.org
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrew+netdev@lunn.ch,
pavan.chebbi@broadcom.com, andrew.gospodarek@broadcom.com,
damodharam.ammepalli@broadcom.com,
kalesh-anakkur.purayil@broadcom.com
Subject: Re: [PATCH net] bnxt_en: Fix aggregation ID mask to prevent oops on 5760X chips
Date: Wed, 11 Dec 2024 02:40:33 +0000 [thread overview]
Message-ID: <173388483328.1093253.13542458074533723016.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241209015448.1937766-1-michael.chan@broadcom.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 8 Dec 2024 17:54:48 -0800 you wrote:
> The 5760X (P7) chip's HW GRO/LRO interface is very similar to that of
> the previous generation (5750X or P5). However, the aggregation ID
> fields in the completion structures on P7 have been redefined from
> 16 bits to 12 bits. The freed up 4 bits are redefined for part of the
> metadata such as the VLAN ID. The aggregation ID mask was not modified
> when adding support for P7 chips. Including the extra 4 bits for the
> aggregation ID can potentially cause the driver to store or fetch the
> packet header of GRO/LRO packets in the wrong TPA buffer. It may hit
> the BUG() condition in __skb_pull() because the SKB contains no valid
> packet header:
>
> [...]
Here is the summary with links:
- [net] bnxt_en: Fix aggregation ID mask to prevent oops on 5760X chips
https://git.kernel.org/netdev/net/c/24c6843b7393
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:[~2024-12-11 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 1:54 [PATCH net] bnxt_en: Fix aggregation ID mask to prevent oops on 5760X chips Michael Chan
2024-12-10 14:59 ` Simon Horman
2024-12-11 2:40 ` 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=173388483328.1093253.13542458074533723016.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew.gospodarek@broadcom.com \
--cc=damodharam.ammepalli@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.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;
as well as URLs for NNTP newsgroup(s).