From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Marco Elver <elver@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
glider@google.com, dvyukov@google.com, eugenis@google.com,
Oscar Salvador <osalvador@suse.de>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: regression/bisected commit 773688a6cb24b0b3c2ba40354d883348a2befa38 make my system completely unusable under high load
Date: Tue, 20 Feb 2024 10:37:03 +0500 [thread overview]
Message-ID: <CABXGCsOHswLa5rd_Q7kHDHESb=BtqB+F=LV7Wvv+qoRxrqCboA@mail.gmail.com> (raw)
In-Reply-To: <7e31accb-db01-486f-afb8-18a3f5402d00@suse.cz>
On Tue, Feb 20, 2024 at 4:50 AM Vlastimil Babka <vbabka@suse.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/
--
Best Regards,
Mike Gavrilov.
next prev parent reply other threads:[~2024-02-20 5:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 10:46 Mikhail Gavrilov
2024-01-19 10:54 ` Marco Elver
2024-01-19 10:59 ` Marco Elver
2024-01-19 17:54 ` Mikhail Gavrilov
2024-01-29 22:25 ` Mikhail Gavrilov
2024-01-29 23:14 ` Andrey Konovalov
2024-02-01 22:08 ` Mikhail Gavrilov
2024-02-02 9:00 ` Marco Elver
2024-02-02 16:35 ` Mikhail Gavrilov
2024-02-02 16:47 ` Marco Elver
2024-02-02 17:19 ` Marco Elver
2024-02-02 20:14 ` Mikhail Gavrilov
2024-02-19 9:48 ` Mikhail Gavrilov
2024-02-19 9:52 ` Marco Elver
2024-02-19 10:09 ` Vlastimil Babka
2024-02-19 23:28 ` Andrew Morton
2024-02-19 23:50 ` Vlastimil Babka
2024-02-20 5:37 ` Mikhail Gavrilov [this message]
2024-02-20 17:30 ` Andrew Morton
2024-02-20 18:16 ` Vlastimil Babka
2024-02-20 18:51 ` Marco Elver
2024-02-26 9:25 ` Marco Elver
2024-02-26 10:12 ` Vlastimil Babka
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='CABXGCsOHswLa5rd_Q7kHDHESb=BtqB+F=LV7Wvv+qoRxrqCboA@mail.gmail.com' \
--to=mikhail.v.gavrilov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=vbabka@suse.cz \
/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