From: Suren Baghdasaryan <surenb@google.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
linux-xfs@vger.kernel.org, linux-mm@kvack.org,
david@fromorbit.com, Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
kasan-dev@googlegroups.com, kdevops@lists.linux.dev
Subject: Re: allocation tagging splats xfs generic/531
Date: Thu, 30 May 2024 18:12:24 -0700 [thread overview]
Message-ID: <CAJuCfpEz+-VeE0-6Z1ks7BTLGmC7JOsM9bHKN5jMqgn9rutmAg@mail.gmail.com> (raw)
In-Reply-To: <ZlkICDI7djlmpYpr@bombadil.infradead.org>
On Thu, May 30, 2024 at 4:13 PM Luis Chamberlain <mcgrof@kernel.org> wrote:
>
> On Thu, May 30, 2024 at 07:03:47PM -0400, Kent Overstreet wrote:
> > this only pops with kasan enabled, so kasan is doing something weird
Thanks for taking a look. I'm back from vacation and will try to dig
up the root cause.
>
> Ok thanks, but it means I gotta disable either mem profiling or kasan. And
> since this is to see what other kernel configs to enable or disable
> to help debug fstests better on kdevops too, kasan seems to win, and
> I suspect I can't be the only other user who might end up concluding the
> same.
To avoid the warning you could disable
CONFIG_MEM_ALLOC_PROFILING_DEBUG until this issue is fixed. This
should allow you to use mem profiling together with kasan.
Thanks,
Suren.
>
> This is easily redproducible by just *boot* on kdevops if you enable
> KASAN and memprofiling today. generic/531 was just another example. So
> hopefully kasan folks have enough info for folks interested to help
> chase it down.
>
> Luis
prev parent reply other threads:[~2024-05-31 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 21:47 Luis Chamberlain
2024-05-30 23:03 ` Kent Overstreet
2024-05-30 23:13 ` Luis Chamberlain
2024-05-31 1:12 ` Suren Baghdasaryan [this message]
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=CAJuCfpEz+-VeE0-6Z1ks7BTLGmC7JOsM9bHKN5jMqgn9rutmAg@mail.gmail.com \
--to=surenb@google.com \
--cc=andreyknvl@gmail.com \
--cc=david@fromorbit.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kdevops@lists.linux.dev \
--cc=kent.overstreet@linux.dev \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=ryabinin.a.a@gmail.com \
--cc=vincenzo.frascino@arm.com \
/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