From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH 6.15 000/588] 6.15.4-rc2 review
Date: Wed, 25 Jun 2025 09:25:29 +0100 [thread overview]
Message-ID: <2025062511-tutor-judiciary-e3f9@gregkh> (raw)
In-Reply-To: <e9249afe-f039-4180-d50d-b199c26dea26@applied-asynchrony.com>
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
next prev parent reply other threads:[~2025-06-25 8:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 12:30 [PATCH 6.15 000/588] 6.15.4-rc2 review Greg Kroah-Hartman
2025-06-24 12:50 ` Ronald Warsow
2025-06-24 14:05 ` Peter Schneider
2025-06-24 17:37 ` Florian Fainelli
2025-06-24 18:34 ` Luna Jernberg
2025-06-24 22:20 ` Christian Heusel
2025-06-25 7:24 ` Jon Hunter
2025-06-25 8:00 ` Holger Hoffstätte
2025-06-25 8:25 ` Greg Kroah-Hartman [this message]
2025-06-25 9:08 ` Holger Hoffstätte
2025-06-25 12:15 ` Barry K. Nathan
2025-06-26 8:59 ` Barry K. Nathan
2025-06-26 10:49 ` Greg Kroah-Hartman
2025-06-25 9:40 ` Takeshi Ogasawara
2025-06-25 10:15 ` Naresh Kamboju
2025-06-25 13:29 ` Justin Forbes
2025-06-25 19:48 ` Mark Brown
2025-06-25 23:16 ` Miguel Ojeda
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=2025062511-tutor-judiciary-e3f9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hargar@microsoft.com \
--cc=holger@applied-asynchrony.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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