From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
kernel-team@meta.com, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [net PATCH 0/5] fbnic: Fix FW crash restore, stop path and mailbox teardown bugs
Date: Tue, 10 Nov 2026 20:40:07 +0000 [thread overview]
Message-ID: <179434320743.48129.3556613330117457794.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <179381496288.9644.9775319757787890210.stgit@ahduyck-xeon-server.home.arpa>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 04 Nov 2026 09:58:59 -0800 you wrote:
> Fixes for races and ordering problems in the paths that take the datapath
> down or rebuild it: the FW crash restore, ndo_stop and PM suspend/resume,
> the Tx force-flush, and the DMA flush on mailbox teardown.
>
> Patches 1-3 were found by code review or inspection; patch 3 has not been
> seen to trigger. Patches 4 and 5 together appear to resolve a hang with a
> PTP Tx timestamp left in flight. The series was tested on fbnic hardware
> with firmware 26.09.14-017_h7ab84d2ef68f, cycling the interface through
> DPC/AER recoveries for a full day, and under QEMU with the fbnic device
> model and live firmware.
>
> [...]
Here is the summary with links:
- [net,1/5] fbnic: Take the instance lock to restore filters after a FW crash
https://git.kernel.org/netdev/net/c/999431e6153d
- [net,2/5] fbnic: Fix service task races with ndo_stop and PM suspend
https://git.kernel.org/netdev/net/c/05ec5504ff69
- [net,3/5] fbnic: Disable PTP completions during the Tx force-flush
https://git.kernel.org/netdev/net/c/7d4568edce74
- [net,4/5] fbnic: Suspend phylink after taking the datapath down in ndo_stop
https://git.kernel.org/netdev/net/c/b45b9c6b83e7
- [net,5/5] fbnic: Wait for the outbound flush to complete on mailbox teardown
https://git.kernel.org/netdev/net/c/c5820a8cf59b
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-11-10 20:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 17:58 [net PATCH 0/5] fbnic: Fix FW crash restore, stop path and mailbox teardown bugs Alexander Duyck
2026-11-04 17:59 ` [net PATCH 1/5] fbnic: Take the instance lock to restore filters after a FW crash Alexander Duyck
2026-11-04 17:59 ` [net PATCH 2/5] fbnic: Fix service task races with ndo_stop and PM suspend Alexander Duyck
2026-11-08 18:32 ` netdev-bot+sashiko
2026-11-09 16:29 ` Alexander Duyck
2026-11-04 17:59 ` [net PATCH 3/5] fbnic: Disable PTP completions during the Tx force-flush Alexander Duyck
2026-11-08 18:32 ` netdev-bot+sashiko
2026-11-04 17:59 ` [net PATCH 4/5] fbnic: Suspend phylink after taking the datapath down in ndo_stop Alexander Duyck
2026-11-08 18:32 ` netdev-bot+sashiko
2026-11-04 17:59 ` [net PATCH 5/5] fbnic: Wait for the outbound flush to complete on mailbox teardown Alexander Duyck
2026-11-08 18:32 ` netdev-bot+sashiko
2026-11-09 16:42 ` Alexander Duyck
2026-11-10 20: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=179434320743.48129.3556613330117457794.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@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