From: Luis Chamberlain <mcgrof@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-xfs@vger.kernel.org, surenb@google.com, 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 16:13:12 -0700 [thread overview]
Message-ID: <ZlkICDI7djlmpYpr@bombadil.infradead.org> (raw)
In-Reply-To: <fkotssj75qj5g5kosjgsewitoiyyqztj2hlxfmgwmwn6pxjhpl@ps57kalkeeqp>
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
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.
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
next prev parent reply other threads:[~2024-05-30 23:13 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 [this message]
2024-05-31 1:12 ` Suren Baghdasaryan
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=ZlkICDI7djlmpYpr@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--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=ryabinin.a.a@gmail.com \
--cc=surenb@google.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