From: Mark Brown <broonie@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Johan Hovold <johan@kernel.org>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Felix Gu <ustc.gu@gmail.com>
Subject: Re: [PATCH] spi: fix use-after-free on managed registration failure
Date: Fri, 27 Mar 2026 16:44:24 +0000 [thread overview]
Message-ID: <acaz6J6-5Cstxu8h@sirena.co.uk> (raw)
In-Reply-To: <acZFnCmcA1UK0xRw@ashevche-desk.local>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
On Fri, Mar 27, 2026 at 10:53:48AM +0200, Andy Shevchenko wrote:
> On Fri, Mar 27, 2026 at 09:47:11AM +0100, Johan Hovold wrote:
> > On Fri, Mar 27, 2026 at 09:20:08AM +0200, Andy Shevchenko wrote:
> > > On Thu, Mar 26, 2026 at 07:25:14PM +0000, Mark Brown wrote:
> > > > Not intentionally?
> > > I don't know, but it allows to start from fixing the users to avoid regressions.
> > > I'm fine with the current state of affairs.
> > The offending commit is already in mainline and hasn't been reverted in
> > Mark's tree. This fix has been merged there though so nothing more is
> > needed for now.
> Ah, I only looked into Linux Next (without looking into the base, which is
> v7.0-rc5 as of today). Thanks for clarification.
Oh, that's a relief! I thought I'd managed to throw some commits away
by mistake.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-03-27 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 14:53 Johan Hovold
2026-03-26 9:35 ` Andy Shevchenko
2026-03-26 19:19 ` Andy Shevchenko
2026-03-26 19:25 ` Mark Brown
2026-03-27 7:20 ` Andy Shevchenko
2026-03-27 8:47 ` Johan Hovold
2026-03-27 8:53 ` Andy Shevchenko
2026-03-27 16:44 ` Mark Brown [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=acaz6J6-5Cstxu8h@sirena.co.uk \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=ustc.gu@gmail.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®