linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marco Elver <elver@google.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: andreyknvl@google.com, glider@google.com, dvyukov@google.com,
	 eugenis@google.com, Oscar Salvador <osalvador@suse.de>,
	Vlastimil Babka <vbabka@suse.cz>,
	 Andrew Morton <akpm@linux-foundation.org>,
	 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: Fri, 19 Jan 2024 11:54:14 +0100	[thread overview]
Message-ID: <CANpmjNN-5PpSQ1A_9aM3u4ei74HuvCoThiLAHi=reXXQwer67A@mail.gmail.com> (raw)
In-Reply-To: <CABXGCsOzpRPZGg23QqJAzKnqkZPKzvieeg=W7sgjgi3q0pBo0g@mail.gmail.com>

On Fri, 19 Jan 2024 at 11:46, Mikhail Gavrilov
<mikhail.v.gavrilov@gmail.com> wrote:
>
> 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@google.com>
> Date:   Mon Nov 20 18:47:19 2023 +0100
>
>     kasan: use stack_depot_put for Generic mode
[...]
>  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?

I was afraid this would happen - could you try this patch series:
https://lore.kernel.org/all/20240118110216.2539519-2-elver@google.com/

Thanks,
-- Marco


  reply	other threads:[~2024-01-19 10:54 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 [this message]
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
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='CANpmjNN-5PpSQ1A_9aM3u4ei74HuvCoThiLAHi=reXXQwer67A@mail.gmail.com' \
    --to=elver@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@google.com \
    --cc=dvyukov@google.com \
    --cc=eugenis@google.com \
    --cc=glider@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mikhail.v.gavrilov@gmail.com \
    --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