From: patchwork-bot+netdevbpf@kernel.org
To: Jamie Bainbridge <jamie.bainbridge@gmail.com>
Cc: nprabudoss@marvell.com, kuba@kernel.org, manishc@marvell.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, manish.rangankar@cavium.com,
Michal.Kalderon@cavium.com, Ariel.Elior@cavium.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net] qed: Don't collect too many protection override GRC elements
Date: Sun, 14 Sep 2025 21:30:06 +0000 [thread overview]
Message-ID: <175788540602.3556271.17651649327034572830.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <f8e1182934aa274c18d0682a12dbaf347595469c.1757485536.git.jamie.bainbridge@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 10 Sep 2025 16:29:16 +1000 you wrote:
> In the protection override dump path, the firmware can return far too
> many GRC elements, resulting in attempting to write past the end of the
> previously-kmalloc'ed dump buffer.
>
> This will result in a kernel panic with reason:
>
> BUG: unable to handle kernel paging request at ADDRESS
>
> [...]
Here is the summary with links:
- [v2,net] qed: Don't collect too many protection override GRC elements
https://git.kernel.org/netdev/net/c/56c0a2a9ddc2
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-09-14 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 6:29 [PATCH v2 net] qed: Don't collect too many protection override GRC elements Jamie Bainbridge
2025-09-14 21:30 ` 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=175788540602.3556271.17651649327034572830.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Ariel.Elior@cavium.com \
--cc=Michal.Kalderon@cavium.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jamie.bainbridge@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manish.rangankar@cavium.com \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=nprabudoss@marvell.com \
--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