From: Jakub Kicinski <kuba@kernel.org>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Simon Horman <horms@kernel.org>,
github@szelinsky.de, o.rempel@pengutronix.de,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 2/2] net: pse-pd: guard regulator ops against freed PI data during unregister
Date: Mon, 10 Aug 2026 13:52:33 -0700 [thread overview]
Message-ID: <20260810135233.4be3dc5d@kernel.org> (raw)
In-Reply-To: <20260810154327.21e71ae9@kmaincent-XPS-13-7390>
On Mon, 10 Aug 2026 15:43:27 +0200 Kory Maincent wrote:
> It would be nice to have it accepted to move forward on your PSE notifier
> series.
>
> Jakub what do you think?
It'd be great if we can figure out the safe lifetime rules for pse-pd
from all entry points. Specifically the sysfs complaint on patch 1
(assuming it's real) makes the series seem like a bit of of a see-saw.
Let's get it reposted and take it from there? We have made significant
changes to our netdev *shiko instance, the new models should squash the
false positives (known on wood).
next prev parent reply other threads:[~2026-08-10 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 12:16 [PATCH net v2 0/2] net: pse-pd: fix use-after-free of PI array on controller unregister Carlo Szelinsky
2026-07-11 12:16 ` [PATCH net v2 1/2] net: pse-pd: stop async event sources before freeing PI data in unregister Carlo Szelinsky
2026-07-17 11:07 ` Simon Horman
2026-08-10 13:19 ` Kory Maincent
2026-07-11 12:16 ` [PATCH net v2 2/2] net: pse-pd: guard regulator ops against freed PI data during unregister Carlo Szelinsky
2026-07-17 11:10 ` Simon Horman
2026-08-10 13:43 ` Kory Maincent
2026-08-10 20:52 ` Jakub Kicinski [this message]
2026-08-12 13:59 ` Carlo Szelinsky
2026-08-13 8:28 ` Kory Maincent
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=20260810135233.4be3dc5d@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=github@szelinsky.de \
--cc=horms@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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®