From: Francesco Dolcini <francesco@dolcini.it>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Francesco Dolcini <francesco@dolcini.it>,
Vignesh Raghavendra <vigneshr@ti.com>,
Amitkumar Karwar <amitkumar.karwar@nxp.com>,
Neeraj Kale <neeraj.sanjaykale@nxp.com>,
Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: Kernel WARNING (RCU) with btnxpuart on TI AM62 platform
Date: Thu, 10 Apr 2025 11:53:20 +0200 [thread overview]
Message-ID: <Z_eVEKQn04-2nhpL@gaggiata.pivistrello.it> (raw)
In-Reply-To: <4107dda8-25fe-4f30-a0e6-906441f9b4c9@molgen.mpg.de>
On Thu, Apr 10, 2025 at 08:34:23AM +0200, Paul Menzel wrote:
> Am 10.04.25 um 08:20 schrieb Francesco Dolcini:
>
> > On Tue, Apr 08, 2025 at 09:15:26PM +0530, Vignesh Raghavendra wrote:
> > > On 08/04/25 14:05, Francesco Dolcini wrote:
> > > > I do have the following kernel warning with 6.15-rc1, on a TI AM62
> > > > platform (arm64), single CPU core, using btnxpuart driver, any idea?
> > > > PREEMPT_RT is enabled, if it matters.
> > > >
> > > > Either the issue is not systematic, or multi cores SoCs are not affected
> > > > (no error on the exact same image on a dual nor on quad core TI AM62).
...
> CVE-2024-26959 [1] has the same trace, and supposedly was fixed by Marcel’s
> commit 664130c0b030 (Bluetooth: btnxpuart: Fix btnxpuart_close) present
> since v6.9-rc1, that is also signed off by you.
It seems that the conclusion at that time was just wrong, the real issue seems
what Vignesh suggested.
Francesco
next prev parent reply other threads:[~2025-04-10 9:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 8:35 Kernel WARNING (RCU) with btnxpuart on TI AM62 platform Francesco Dolcini
2025-04-08 9:26 ` Paul Menzel
2025-04-08 9:35 ` Francesco Dolcini
2025-04-08 15:45 ` Vignesh Raghavendra
2025-04-10 6:20 ` Francesco Dolcini
2025-04-10 6:34 ` Paul Menzel
2025-04-10 6:48 ` Paul Menzel
2025-04-10 6:51 ` Paul Menzel
2025-04-10 9:53 ` Francesco Dolcini [this message]
2025-05-12 14:47 ` Paul Menzel
2025-05-23 8:07 ` Francesco Dolcini
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=Z_eVEKQn04-2nhpL@gaggiata.pivistrello.it \
--to=francesco@dolcini.it \
--cc=amitkumar.karwar@nxp.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=neeraj.sanjaykale@nxp.com \
--cc=nm@ti.com \
--cc=pmenzel@molgen.mpg.de \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.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