linux-kernel - Re: regression/bisected commit 773688a6cb24b0b3c2ba40354d883348a2befa38 make my system completely unusable under high load

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]

Date: Tue, 20 Feb 2024 09:30:11 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
Cc: Vlastimil Babka <vbabka@...e.cz>, Marco Elver <elver@...gle.com>, Andrey
 Konovalov <andreyknvl@...il.com>, glider@...gle.com, dvyukov@...gle.com,
 eugenis@...gle.com, Oscar Salvador <osalvador@...e.de>, Linux List Kernel
 Mailing <linux-kernel@...r.kernel.org>, Linux Memory Management List
 <linux-mm@...ck.org>
Subject: Re: regression/bisected commit
 773688a6cb24b0b3c2ba40354d883348a2befa38 make my system completely unusable
 under high load

On Tue, 20 Feb 2024 10:37:03 +0500 Mikhail Gavrilov <mikhail.v.gavrilov@...il.com> wrote:

> On Tue, Feb 20, 2024 at 4:50 AM Vlastimil Babka <vbabka@...e.cz> wrote:
> > >
> > > I'm all confused.
> > >
> > > 4434a56ec209 ("stackdepot: make fast paths lock-less again") was
> > > mainlined for v6.8-rc3.
> >
> > Uh sorry, I just trusted the info that it's not merged and didn't verify
> > it myself. Yeah, I can see it is there.
> >
> 
> Wait, I am talk about these two patches which is not merged yet:
> [PATCH v2 1/2] stackdepot: use variable size records for non-evictable entries
> [PATCH v2 2/2] kasan: revert eviction of stack traces in generic mode
> https://lore.kernel.org/linux-mm/20240129100708.39460-1-elver@google.com/

A can move those into the 6.8-rc hotfixes queue, and it appears a
cc:stable will not be required.

However I'm not seeing anything in the changelogs to indicate that
we're fixing a dramatic performance regression, nor why that
regressions is occurring.