From: Christoph Hellwig <hch@infradead.org>
To: linux-btrfs@vger.kernel.org
Subject: btrfs/071 is unhappy on 6.18-rc2
Date: Mon, 20 Oct 2025 00:22:55 -0700 [thread overview]
Message-ID: <aPXjTw8WN5Jlv2ho@infradead.org> (raw)
I just kicked off a baseline run with the xfstests volume group and
a SCRATCH_DEV_POOL with 5 virtual nvme devices to test a VFS change that
affects іt a little, and it does not seem too happy.
btrfs/071 gets into slab poisoning:
[ 279.241695] BTRFS info (device nvme1n1 state M): use zlib compression, level 3
[ 279.247651] Oops: general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b6d73:I
[ 279.250656] CPU: 1 UID: 0 PID: 82037 Comm: btrfs-cleaner Tainted: GN 6.18.0-rc2
[ 279.250656] Tainted: [N]=TEST
[ 279.250656] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/4
[ 279.250656] RIP: 0010:btrfs_kill_all_delayed_nodes+0x145/0x1e0
[ 279.250656] Code: 08 48 c1 e5 03 4b 8b 5c 3d 00 48 89 df e8 23 d0 ff ff 48 85 db 74 0f 4a 8d 54 3c0
[ 279.250656] RSP: 0018:ffffc9000138bdc0 EFLAGS: 00010246
[ 279.250656] RAX: 6b6b6b6b6b6b6b6b RBX: ffff88810dad3d58 RCX: 0000000000000000
[ 279.250656] RDX: 0000000000000001 RSI: 0000000000000286 RDI: 00000000ffffffff
[ 279.250656] RBP: 0000000000000008 R08: ffff88810dad3f60 R09: ffff88810dad3f10
[ 279.250656] R10: 000000000000000d R11: ffff88810dad3d58 R12: ffff88811bdfbc18
[ 279.250656] R13: ffffc9000138bdc8 R14: ffff88811bdfb800 R15: 0000000000000000
[ 279.250656] FS: 0000000000000000(0000) GS:ffff8883ef66a000(0000) knlGS:0000000000000000
[ 279.250656] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 279.250656] CR2: 00007fcba10194c8 CR3: 00000001217a3002 CR4: 0000000000772ef0
[ 279.250656] PKRU: 55555554
[ 279.250656] Call Trace:
[ 279.250656] <TASK>
[ 279.250656] ? __schedule+0x52c/0xb60
[ 279.250656] btrfs_clean_one_deleted_snapshot+0x72/0x100
[ 279.250656] cleaner_kthread+0xd3/0x150
[ 279.250656] ? __pfx_cleaner_kthread+0x10/0x10
[ 279.250656] kthread+0x109/0x220
[ 279.250656] ? __pfx_kthread+0x10/0x10
[ 279.250656] ? __pfx_kthread+0x10/0x10
[ 279.250656] ret_from_fork+0x120/0x160
[ 279.250656] ? __pfx_kthread+0x10/0x10
[ 279.250656] ret_from_fork_asm+0x1a/0x30
[ 279.250656] </TASK>
[ 279.250656] Modules linked in: kvm_intel kvm irqbypass
[ 279.277534] ---[ end trace 0000000000000000 ]---
similar things repeat a few times, and then it loops basically forever
doing device replacements, I waited for 30 minutes before killing it.
next reply other threads:[~2025-10-20 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 7:22 Christoph Hellwig [this message]
2025-10-20 9:11 ` btrfs/071 is unhappy on 6.18-rc2 Qu Wenruo
2025-10-20 9:46 ` Christoph Hellwig
2025-10-20 10:26 ` Qu Wenruo
2025-10-20 14:19 ` Christoph Hellwig
2025-10-20 16:55 ` Leo Martins
2025-10-20 23:25 ` Leo Martins
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=aPXjTw8WN5Jlv2ho@infradead.org \
--to=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.