From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
stable@vger.kernel.org, Frank Li <Frank.Li@nxp.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [REGRESSION] v6.6.120: i3c crash caused by commit 82a09b9965ed
Date: Wed, 21 Jan 2026 17:57:38 +0100 [thread overview]
Message-ID: <202601211657387e890711@mail.local> (raw)
In-Reply-To: <2026012139-fidgeting-comic-916c@gregkh>
On 21/01/2026 15:56:01+0100, Greg Kroah-Hartman wrote:
> On Wed, Jan 21, 2026 at 08:04:03PM +0900, Kunihiko Hayashi wrote:
> > Dear stable maintainers,
> >
> > After updating from v6.6.119 to v6.6.120, I noticed a kernel crash
> > when I3C was enabled.
> >
> > This regression is caused by:
> >
> > commit 82a09b9965ed ("i3c: fix refcount inconsistency in i3c_master_register")
> >
> > The issue is resolved when the following upstream fix commit is applied:
> >
> > commit 3502cea99c7c ("i3c: Move device name assignment after i3c_bus_init")
>
> That does not seem to be a valid git id, where did it come from?
>
This has not yet been sent to Linus and my plan was to wait for the
merge window as the fix didn't make it clear this was actually happening
in the field.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-01-21 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 11:04 [REGRESSION] v6.6.120: i3c crash caused by commit 82a09b9965ed Kunihiko Hayashi
2026-01-21 14:56 ` Greg Kroah-Hartman
2026-01-21 16:57 ` Alexandre Belloni [this message]
2026-01-21 17:20 ` Greg Kroah-Hartman
2026-01-22 5:58 ` Kunihiko Hayashi
2026-03-04 9:19 ` Kunihiko Hayashi
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=202601211657387e890711@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=Frank.Li@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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