linux-kernel - Re: [PATCH printk v2 2/2] printk: Avoid scheduling irq

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 for Android: free password hash cracker in your pocket

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

Message-ID: <aSbG4lo2cFbwytTF@pathway.suse.cz>
Date: Wed, 26 Nov 2025 10:22:42 +0100
From: Petr Mladek <pmladek@...e.com>
To: Derek Barbosa <debarbos@...hat.com>
Cc: John Ogness <john.ogness@...utronix.de>,
	Sergey Senozhatsky <senozhatsky@...omium.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Sherry Sun <sherry.sun@....com>, Jacky Bai <ping.bai@....com>,
	Jon Hunter <jonathanh@...dia.com>,
	Thierry Reding <thierry.reding@...il.com>,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH printk v2 2/2] printk: Avoid scheduling irq_work on
 suspend

On Tue 2025-11-25 14:24:55, Derek Barbosa wrote:
> On Thu, Nov 13, 2025 at 02:15:09PM -0500, Derek Barbosa wrote:
> > Hi John,
> > 
> > On Thu, Nov 13, 2025 at 06:12:57PM +0106, John Ogness wrote:
> > > 
> > > I assume the problem you are seeing is with the PREEMPT_RT patches
> > > applied (i.e. with the 8250-NBCON included). If that is the case, note
> > > that recent versions of the 8250 driver introduce its own irq_work that
> > > is also problematic. I am currently reworking the 8250-NBCON series so
> > > that it does not introduce irq_work.
> > > 
> 
> 
> Hi John,
> 
> Apologies for the late reply here. Just now got some results in.

No problem at all.

> Testing this patch series atop of Linus' tree resolves the suspend issue seen on
> these large CPU workstation systems.

Thanks a lot for checking the patches. It is great to know that it
resolved the problem.

> I see this has already landed in the maintainers tree at printk/linux.git.

Yes, I wanted to have it in linux-next in time before the merge window opens
for 6.19 (likely next week).

Best Regards,
Petr