From: patchwork-bot+netdevbpf@kernel.org
To: Myeonghun Pak <mhun512@gmail.com>
Cc: shenjian15@huawei.com, shaojijie@huawei.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ae878000@gmail.com
Subject: Re: [PATCH net] net: hix5hd2: serialize timeout recovery with interface teardown
Date: Tue, 20 Oct 2026 20:10:17 +0000 [thread overview]
Message-ID: <179252701752.186787.4792188707479278669.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <179203116093.2621539.3718842986255459438.G202@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 14 Oct 2026 22:26:35 -0400 you wrote:
> The timeout worker calls the driver's close and open methods without
> RTNL or a running-state check. A timeout queued before an interface is
> closed can call close again after ndo_stop has disabled NAPI. The second
> napi_disable() can then wait indefinitely. The worker can also race with
> an ongoing close.
>
> Take RTNL and skip recovery when the interface is no longer running.
> Use the netdev core close and open helpers so a failed reopen leaves the
> interface down, rather than leaving it marked running with NAPI disabled.
>
> [...]
Here is the summary with links:
- [net] net: hix5hd2: serialize timeout recovery with interface teardown
https://git.kernel.org/netdev/net-next/c/87cce46329a8
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:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 2:26 [PATCH net] net: hix5hd2: serialize timeout recovery with interface teardown Myeonghun Pak
2026-10-19 2:29 ` netdev-bot+sashiko
2026-10-19 7:29 ` Jijie Shao
2026-10-20 20: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=179252701752.186787.4792188707479278669.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ae878000@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhun512@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shaojijie@huawei.com \
--cc=shenjian15@huawei.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