From: patchwork-bot+netdevbpf@kernel.org
To: David Yang <mmyangfl@gmail.com>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org,
shenjian15@huawei.com, shaojijie@huawei.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, lidongpo@hisilicon.com,
xuejiancheng@hisilicon.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: hisilicon: hisi_femac: Stop the receiver before releasing the RX ring
Date: Tue, 27 Oct 2026 23:10:06 +0000 [thread overview]
Message-ID: <179314260682.383254.18077445716959126506.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261025182022.2959333-1-mmyangfl@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 26 Oct 2026 02:20:18 +0800 you wrote:
> hisi_femac_net_close() frees the receive ring while the RX address queue
> still holds every address that was pushed to IQ_ADDR.
>
> A port that keeps receiving then DMAs arrived frames into buffers that
> other slab caches have already taken back; on an EC6108V9C (hi3798mv100)
> the queue still held all 52 armed addresses right after the interface
> was closed, and had dropped to 43 after 15 s of broadcast traffic.
>
> [...]
Here is the summary with links:
- [net] net: hisilicon: hisi_femac: Stop the receiver before releasing the RX ring
https://git.kernel.org/netdev/net/c/d54b21d82430
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 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 18:20 [PATCH net] net: hisilicon: hisi_femac: Stop the receiver before releasing the RX ring David Yang
2026-10-27 23:10 ` 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=179314260682.383254.18077445716959126506.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=lidongpo@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmyangfl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shaojijie@huawei.com \
--cc=shenjian15@huawei.com \
--cc=stable@vger.kernel.org \
--cc=xuejiancheng@hisilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.