linux-kernel - RE: [PATCH 04/19] serial: sh-sci: Fix deadlock during RSCI FIFO overrun error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <TYCPR01MB113326A115358BB084F0CEC2186FDA@TYCPR01MB11332.jpnprd01.prod.outlook.com>
Date: Tue, 28 Oct 2025 09:08:56 +0000
From: Biju Das <biju.das.jz@...renesas.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: Jiri Slaby <jirislaby@...nel.org>, Geert Uytterhoeven
	<geert+renesas@...der.be>, Prabhakar Mahadev Lad
	<prabhakar.mahadev-lad.rj@...renesas.com>, wsa+renesas
	<wsa+renesas@...g-engineering.com>, Claudiu Beznea
	<claudiu.beznea.uj@...renesas.com>, Nam Cao <namcao@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>, biju.das.au
	<biju.das.au@...il.com>, "linux-renesas-soc@...r.kernel.org"
	<linux-renesas-soc@...r.kernel.org>, "stable@...nel.org" <stable@...nel.org>
Subject: RE: [PATCH 04/19] serial: sh-sci: Fix deadlock during RSCI FIFO
 overrun error

Hi Greg,

Thanks for the feedback.

> -----Original Message-----
> From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Sent: 28 October 2025 08:41
> Subject: Re: [PATCH 04/19] serial: sh-sci: Fix deadlock during RSCI FIFO overrun error
> 
> On Mon, Oct 27, 2025 at 03:45:51PM +0000, Biju Das wrote:
> > On RSCI IP, a deadlock occurs during a FIFO overrun error, as it uses
> > a different register to clear the FIFO overrun error status.
> >
> > Cc: stable@...nel.org
> > Fixes: 0666e3fe95ab ("serial: sh-sci: Add support for RZ/T2H SCI")
> > Signed-off-by: Biju Das <biju.das.jz@...renesas.com>
> 
> Why is patch 4/19 the only one marked for stable backports?  That feels really wrong as that will not
> show up until after 6.19-rc1 is out, AND the dependant patches will also not be backported.
> 

My bad, I will send this patch as a separate one.

> Please split up patch series to have "things that must be merged now"
> separate from "these are for the next -rc1 release"

OK. Will separate this in next version.

Cheers,
Biju