From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Machon <daniel.machon@microchip.com>
Cc: Steen.Hegelund@microchip.com, UNGLinuxDriver@microchip.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horatiu.vultur@microchip.com,
jensemil.schulzostergaard@microchip.com,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: microchip: fdma: fix DCB corruption under sustained load
Date: Tue, 27 Oct 2026 22:30:05 +0000 [thread overview]
Message-ID: <179314020569.360855.3209955034452568131.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261026-microchip-fdma-dcb-corruption-v1-1-36dab6caca07@microchip.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 26 Oct 2026 14:47:05 +0100 you wrote:
> __fdma_dcb_add() prepares a DCB and links it into a channel's chain by
> writing its address to the NEXT_PTR of the current last DCB. The FDMA
> may be processing the chain while this happens.
>
> Before this patch, the link is written before the new DCB's own nextptr
> and info fields, so the FDMA can follow it to a DCB that hasn't been fully
> prepared yet. Under sustained load this stalls the FDMA.
>
> [...]
Here is the summary with links:
- [net] net: microchip: fdma: fix DCB corruption under sustained load
https://git.kernel.org/netdev/net/c/573a6d4c7a21
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-10-27 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 13:47 [PATCH net] net: microchip: fdma: fix DCB corruption under sustained load Daniel Machon
2026-10-27 22: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=179314020569.360855.3209955034452568131.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=jensemil.schulzostergaard@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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