linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <CABXGCsOzpRPZGg23QqJAzKnqkZPKzvieeg=W7sgjgi3q0pBo0g@mail.gmail.com>
Date: Fri, 19 Jan 2024 15:46:31 +0500
From: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
To: andreyknvl@...gle.com, elver@...gle.com, glider@...gle.com, 
	dvyukov@...gle.com, eugenis@...gle.com, Oscar Salvador <osalvador@...e.de>, 
	Vlastimil Babka <vbabka@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>, 
	Linux List Kernel Mailing <linux-kernel@...r.kernel.org>, 
	Linux Memory Management List <linux-mm@...ck.org>
Subject: regression/bisected commit 773688a6cb24b0b3c2ba40354d883348a2befa38
 make my system completely unusable under high load

Hi,
I use a system with KASAN sanitizer everyday.
Because I want to catch difficult-to-repeat bugs.
And all worked fine until commit 773688a6cb24b0b3c2ba40354d883348a2befa38.
After commit 773688a6cb24b0b3c2ba40354d883348a2befa38 all working
jerky when I compile something.
The sound is interrupted, the cursor moves jerkily if I try to do
anything when all the cores are loaded.

> git bisect bad
773688a6cb24b0b3c2ba40354d883348a2befa38 is the first bad commit
commit 773688a6cb24b0b3c2ba40354d883348a2befa38
Author: Andrey Konovalov <andreyknvl@...gle.com>
Date:   Mon Nov 20 18:47:19 2023 +0100

    kasan: use stack_depot_put for Generic mode

    Evict alloc/free stack traces from the stack depot for Generic KASAN once
    they are evicted from the quaratine.

    For auxiliary stack traces, evict the oldest stack trace once a new one is
    saved (KASAN only keeps references to the last two).

    Also evict all saved stack traces on krealloc.

    To avoid double-evicting and mis-evicting stack traces (in case KASAN's
    metadata was corrupted), reset KASAN's per-object metadata that stores
    stack depot handles when the object is initialized and when it's evicted
    from the quarantine.

    Note that stack_depot_put is no-op if the handle is 0.

    Link: https://lkml.kernel.org/r/5cef104d9b842899489b4054fe8d1339a71acee0.1700502145.git.andreyknvl@google.com
    Signed-off-by: Andrey Konovalov <andreyknvl@...gle.com>
    Reviewed-by: Marco Elver <elver@...gle.com>
    Cc: Alexander Potapenko <glider@...gle.com>
    Cc: Dmitry Vyukov <dvyukov@...gle.com>
    Cc: Evgenii Stepanov <eugenis@...gle.com>
    Cc: Oscar Salvador <osalvador@...e.de>
    Cc: Vlastimil Babka <vbabka@...e.cz>
    Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>

 mm/kasan/common.c     |  3 ++-
 mm/kasan/generic.c    | 22 ++++++++++++++++++----
 mm/kasan/quarantine.c | 26 ++++++++++++++++++++------
 3 files changed, 40 insertions(+), 11 deletions(-)

I attached here my build .config and kernel log.
Who could dig into it, please?

-- 
Best Regards,
Mike Gavrilov.

Download attachment ".config.zip" of type "application/zip" (65161 bytes)

Download attachment "bisect-performance-regression-KASAN-log.zip" of type "application/zip" (1239 bytes)

Download attachment "dmesg-performance-regression-KASAN.zip" of type "application/zip" (44240 bytes)