linux-kernel - Re: [PATCH 6.15 000/588] 6.15.4-rc2 review

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: <2025062511-tutor-judiciary-e3f9@gregkh>
Date: Wed, 25 Jun 2025 09:25:29 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Holger Hoffstätte <holger@...lied-asynchrony.com>
Cc: stable@...r.kernel.org, patches@...ts.linux.dev,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
	patches@...nelci.org, lkft-triage@...ts.linaro.org, pavel@...x.de,
	jonathanh@...dia.com, f.fainelli@...il.com,
	sudipm.mukherjee@...il.com, srw@...dewatkins.net, rwarsow@....de,
	conor@...nel.org, hargar@...rosoft.com, broonie@...nel.org,
	Christian Brauner <brauner@...nel.org>
Subject: Re: [PATCH 6.15 000/588] 6.15.4-rc2 review

On Wed, Jun 25, 2025 at 10:00:56AM +0200, Holger Hoffstätte wrote:
> (cc: Christian Brauner>
> 
> Since 6.15.4-rc1 I noticed that some KDE apps (kded6, kate (the text editor))
> started going into a tailspin with 100% per-process CPU.
> 
> The symptom is 100% reproducible: open a new file with kate, save empty file,
> make changes, save, watch CPU go 100%. perf top shows copy_to_user running wild.
> 
> First I tried to reproduce on 6.15.3 - no problem, everything works fine.
> 
> After checking the list of patches for 6.15.4 I reverted the anon_inode series
> (all 3 for the first attempt) and the problem is gone.
> 
> Will try to reduce further & can gladly try additional fixes, but for now
> I'd say these patches are not yet suitable for stable.

Does this same issue also happen for you on 6.16-rc3?

thanks,

greg k-h