From: Christoph Hellwig <hch@infradead.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
cl@linux.com, glittao@gmail.com, iamjoonsoo.kim@lge.com,
linux-mm@kvack.org, mm-commits@vger.kernel.org,
penberg@kernel.org, rdunlap@infradead.org, rientjes@google.com,
torvalds@linux-foundation.org, linux-xfs@vger.kernel.org
Subject: Re: [patch 07/54] mm/slub: use stackdepot to save stack trace in objects
Date: Fri, 16 Jul 2021 10:12:27 +0100 [thread overview]
Message-ID: <YPFNe6ZkIa8aciF3@infradead.org> (raw)
In-Reply-To: <8b9315cd-bf72-6ffe-a2c4-1e84d7375225@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
On Fri, Jul 16, 2021 at 10:57:51AM +0200, Vlastimil Babka wrote:
> On 7/16/21 9:39 AM, Christoph Hellwig wrote:
> > This somewhat unexpectedly causes a crash when running the xfs/433 test
> > in xfstests for me. Reverting the commit fixes the problem:
>
> That's weird, the backtrace doesn't even include SLUB/stackdepot code.
> Is that kernel actually booted with slub_debug option/built with
> CONFIG_SLUB_DEBUG_ON or some cache created with SLAB_STORE_USER ?
CONFIG_SLUB_DEBUG_ON is enabled, yes. Full .config attached.
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 35959 bytes --]
next prev parent reply other threads:[~2021-07-16 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210707175950.eceddb86c6c555555d4730e2@linux-foundation.org>
[not found] ` <20210708010747.zIP9yxsci%akpm@linux-foundation.org>
2021-07-16 7:39 ` [patch 07/54] mm/slub: use stackdepot to save stack trace in objects Christoph Hellwig
2021-07-16 8:57 ` Vlastimil Babka
2021-07-16 9:12 ` Christoph Hellwig [this message]
2021-07-16 20:12 ` Linus Torvalds
2021-07-16 22:37 ` Vlastimil Babka
2021-07-17 17:34 ` Randy Dunlap
2021-07-18 7:29 ` Vlastimil Babka
2021-07-18 14:17 ` Randy Dunlap
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=YPFNe6ZkIa8aciF3@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=glittao@gmail.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).