From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Golle <daniel@makrotopia.org>
Cc: andrew@lunn.ch, olteanv@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
linux@armlinux.org.uk, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: dsa: mxl862xx: disable the stats poll on teardown
Date: Tue, 15 Sep 2026 02:20:03 +0000 [thread overview]
Message-ID: <178943880364.1318657.7386194334334318104.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1eb6f7fc1789b67e4b11e3f4d5ff080d0b6f7cbb.1789045590.git.daniel@makrotopia.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 10 Sep 2026 14:13:15 +0100 you wrote:
> mxl862xx_setup() arms the stats poll before mxl862xx_setup_mdio(), and
> nothing stops it until dsa_register_switch() has returned an error to
> mxl862xx_probe(). DSA frees the dsa_port list before it returns, so a
> poll that fires once .setup or a later step of dsa_tree_setup() has
> failed walks freed ports. On shutdown the user ports stay registered,
> and the WORK_STOPPED flag test in mxl862xx_get_stats64() is not atomic
> with the cancel in mxl862xx_shutdown(), so a re-arm that read the flag
> before it was set queues the poll after cancel_delayed_work_sync() has
> returned.
>
> [...]
Here is the summary with links:
- [net,v2] net: dsa: mxl862xx: disable the stats poll on teardown
https://git.kernel.org/netdev/net/c/9e92ad4630f5
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-09-15 2:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 13:13 Daniel Golle
2026-09-15 2:20 ` 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=178943880364.1318657.7386194334334318104.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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
all inboxes | Powered by JetHome®