From: patchwork-bot+netdevbpf@kernel.org
To: Sagi Maimon <maimon.sagi@gmail.com>
Cc: netdev@vger.kernel.org, radhey.shyam.pandey@amd.com,
michal.simek@amd.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
andre.przywara@arm.com, robert.hancock@calian.com,
horms@kernel.org, joe@dama.to, suraj.gupta2@amd.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: axienet: release every RX buffer in axienet_dma_bd_release()
Date: Tue, 20 Oct 2026 20:50:10 +0000 [thread overview]
Message-ID: <179252941027.202014.1920735438863244312.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261015084743.1798326-1-maimon.sagi@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 15 Oct 2026 11:47:43 +0300 you wrote:
> The RX walk in axienet_dma_bd_release() stops at the first descriptor
> without an skb, assuming that such a slot and all after it were never
> filled. That holds on the axienet_dma_bd_init() error path, but not once
> the ring has been running: when axienet_rx_poll() fails to allocate or
> map a replacement buffer it leaves the slot it emptied with a NULL skb,
> in the middle of a populated ring, until a later poll refills it.
> Closing the interface before then leaks the skb and the streaming DMA
> mapping of every descriptor after that slot, which can be most of the
> ring, and is most likely under memory pressure.
>
> [...]
Here is the summary with links:
- [net-next] net: axienet: release every RX buffer in axienet_dma_bd_release()
https://git.kernel.org/netdev/net-next/c/b59787892d04
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-20 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 8:47 [PATCH net-next] net: axienet: release every RX buffer in axienet_dma_bd_release() Sagi Maimon
2026-10-20 20:50 ` 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=179252941027.202014.1920735438863244312.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andre.przywara@arm.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=joe@dama.to \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maimon.sagi@gmail.com \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=robert.hancock@calian.com \
--cc=suraj.gupta2@amd.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