From: patchwork-bot+netdevbpf@kernel.org
To: Anshumali Gaur <agaur@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jacob.e.keller@intel.com, sgoutham@marvell.com,
lcherian@marvell.com, gakula@marvell.com, jerinj@marvell.com,
hkelam@marvell.com, sbhatta@marvell.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH v2] octeontx2-af: Fix PF driver crash with kexec kernel booting
Date: Thu, 05 Feb 2026 21:00:08 +0000 [thread overview]
Message-ID: <177032520833.564062.4499148622952657788.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260203050701.2616685-1-agaur@marvell.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 3 Feb 2026 10:37:01 +0530 you wrote:
> During a kexec reboot the hardware is not power-cycled, so AF state from
> the old kernel can persist into the new kernel. When AF and PF drivers
> are built as modules, the PF driver may probe before AF reinitializes
> the hardware.
>
> The PF driver treats the RVUM block revision as an indication that AF
> initialization is complete. If this value is left uncleared at shutdown,
> PF may incorrectly assume AF is ready and access stale hardware state,
> leading to a crash.
>
> [...]
Here is the summary with links:
- [v2] octeontx2-af: Fix PF driver crash with kexec kernel booting
https://git.kernel.org/netdev/net/c/2d2d574309e3
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-02-05 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 5:07 [PATCH v2] octeontx2-af: Fix PF driver crash with kexec kernel booting Anshumali Gaur
2026-02-05 21:00 ` 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=177032520833.564062.4499148622952657788.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agaur@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jacob.e.keller@intel.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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