From: Matthew Wilcox <willy@infradead.org>
To: Calvin Owens <calvin@wbinvd.org>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: [BUG next-20260105] khugepaged: kernel BUG at ./include/linux/xarray.h:1441
Date: Mon, 5 Jan 2026 18:24:30 +0000 [thread overview]
Message-ID: <aVwB3t2wD6Dyt6yT@casper.infradead.org> (raw)
In-Reply-To: <aVvz3tYdu49TGkjI@mozart.vkv.me>
On Mon, Jan 05, 2026 at 09:24:46AM -0800, Calvin Owens wrote:
> Hello all,
>
> I'm hitting this BUG_ON consistently after boot on next-20260105:
>
> [ 17.103774][ T40] node ffff888102d43918 offset 0 parent ffff888102d42920 shift 0 count 64 values 0 array ffff888107432e38 list ffff888102d43930 ffff888102d43930 marks 0 0 0
> [ 17.108851][ T40] ------------[ cut here ]------------
> [ 17.110476][ T40] kernel BUG at ./include/linux/xarray.h:1441!
> [ 17.112321][ T40] Oops: invalid opcode: 0000 [#1] SMP PTI
> [ 17.114177][ T40] CPU: 1 UID: 0 PID: 40 Comm: khugepaged Not tainted 6.19.0-rc4-next-20260105-x86-hardened-yugetlb #1 PREEMPTLAZY a1685c863f468289fb411d1c9b04bc9e336fe015
> [ 17.118934][ T40] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-20240910_120124-localhost 04/01/2014
> [ 17.122375][ T40] RIP: 0010:hpage_collapse_scan_file+0x1b05/0x1b30
Could you run this through ./scripts/decode_stacktrace.sh ? I'd like
to see which caller of xas_lock() triggered this.
next prev parent reply other threads:[~2026-01-05 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 17:24 Calvin Owens
2026-01-05 17:51 ` Andrew Morton
2026-01-05 18:10 ` Calvin Owens
2026-01-05 18:31 ` Matthew Wilcox
2026-01-05 18:24 ` Matthew Wilcox [this message]
2026-01-05 18:48 ` Calvin Owens
2026-01-05 19:22 ` Matthew Wilcox
2026-01-05 19:54 ` Shivank Garg
2026-01-05 21:02 ` Matthew Wilcox
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=aVwB3t2wD6Dyt6yT@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=calvin@wbinvd.org \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.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