From: Carlo Szelinsky <github@szelinsky.de>
To: netdev-bot+sashiko@kernel.org
Cc: o.rempel@pengutronix.de, kory.maincent@bootlin.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, broonie@kernel.org,
lgirdwood@gmail.com, corey@leavitt.info, kyle.swenson@est.tech,
horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, sashiko-reviews@lists.linux.dev
Subject: Re: [PATCH net-next 1/4] net: pse-pd: unlink the controller before freeing its PI data
Date: Mon, 19 Oct 2026 21:56:06 +0200 [thread overview]
Message-ID: <20261019195606.307851-1-github@szelinsky.de> (raw)
In-Reply-To: <179239893644.3135.4909831916521856844@kernel.org>
On Mon, 19 Oct 2026 08:35:36 +0000, netdev-bot+sashiko@kernel.org wrote:
> [Severity: Low]
> Should this have a Fixes: tag?
Yes. The patch moves to net, where it gets Fixes tags.
> [Severity: Medium]
> This isn't a bug introduced by this patch, but is the IRQ passed to
> disable_irq() here always one the controller owns?
No. That is an older bug, fixed in net by "net: pse-pd: do not keep a
failed IRQ in pcdev->irq".
> [Severity: High]
> Unlinking from pse_controller_list blocks new of_pse_control_get()
> lookups. What about the pse_control handles that consumers already hold?
Right, that is an older bug, and this commit message claims too much.
The PSE notifier series fixes it: there, the PHYs drop their handles
before the PI data is freed. In net, this patch is replaced by two
patches of [1]; the cover letter of [1] says that this case is not
fixed there.
> [Severity: High]
> Can ntf_work be queued again after this cancel_work_sync()?
Yes, through a handle that a consumer still holds, so this is the same
older bug as above. The notifier series cancels the work only after
all handles are dropped.
> [Severity: High]
> Can the PI regulators still use pcdev->pi after pse_release_pis() frees
> it here?
Yes, an older bug. It is fixed by the second patch of [1], which I
will rework and fold into the net series.
[1] https://lore.kernel.org/netdev/20260813200653.980170-1-github@szelinsky.de/
Carlo
next prev parent reply other threads:[~2026-10-19 19:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 8:18 [PATCH net-next 0/4] net: pse-pd: core fixes ahead of the controller notifier Carlo Szelinsky
2026-10-18 8:18 ` [PATCH net-next 1/4] net: pse-pd: unlink the controller before freeing its PI data Carlo Szelinsky
2026-10-19 8:35 ` netdev-bot+sashiko
2026-10-19 19:56 ` Carlo Szelinsky [this message]
2026-10-18 8:18 ` [PATCH net-next 2/4] net: pse-pd: unwind allocations when controller registration fails Carlo Szelinsky
2026-10-19 8:35 ` netdev-bot+sashiko
2026-10-19 19:56 ` Carlo Szelinsky
2026-10-18 8:18 ` [PATCH net-next 3/4] net: pse-pd: si3474: use dev_err_probe() for controller registration Carlo Szelinsky
2026-10-18 8:18 ` [PATCH net-next 4/4] net: pse-pd: check the PI vpwr supply before registering the controller Carlo Szelinsky
2026-10-19 8:35 ` netdev-bot+sashiko
2026-10-19 19:56 ` Carlo Szelinsky
2026-10-18 8:23 ` [PATCH net-next 0/4] net: pse-pd: core fixes ahead of the controller notifier netdev-bot+sinfo
2026-10-19 19:56 ` Carlo Szelinsky
2026-10-19 12:54 ` Kory Maincent
2026-10-19 19:55 ` Carlo Szelinsky
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=20261019195606.307851-1-github@szelinsky.de \
--to=github@szelinsky.de \
--cc=andrew+netdev@lunn.ch \
--cc=broonie@kernel.org \
--cc=corey@leavitt.info \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=kyle.swenson@est.tech \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
/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.