From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs/071 is unhappy on 6.18-rc2
Date: Mon, 20 Oct 2025 02:46:56 -0700 [thread overview]
Message-ID: <aPYFECiBrh36AwtB@infradead.org> (raw)
In-Reply-To: <9093d4c3-b707-4ef1-be48-36578ac1d2f3@gmx.com>
On Mon, Oct 20, 2025 at 07:41:03PM +1030, Qu Wenruo wrote:
> > [ 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
>
> Any line number/context
Nope, that's it. Last lines before are:
[ 62.492209] BTRFS info (device nvme1n1): first mount of filesystem 975f6fd4-b50f-4f3d-8112-319c
[ 62.492520] BTRFS info (device nvme1n1): using crc32c (crc32c-lib) checksum algorithm
[ 62.510951] BTRFS info (device nvme1n1): checking UUID tree
[ 62.511230] BTRFS info (device nvme1n1): enabling ssd optimizations
[ 62.511452] BTRFS info (device nvme1n1): turning on async discard
[ 62.511728] BTRFS info (device nvme1n1): enabling free space tree
[ 62.642011] BTRFS info (device nvme1n1 state M): use zlib compression, level 3
> and reproducibility?
100% over a few runs.
> If you're able to reproduce, mind to try KASAN?
> As I just checked my logs, no failures on btrfs/071 recorded yet (but not on
> upstream rc2 yet)
A bit busy right now, but I'll try to do a KASAN run later.
next prev parent reply other threads:[~2025-10-20 9:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 7:22 btrfs/071 is unhappy on 6.18-rc2 Christoph Hellwig
2025-10-20 9:11 ` Qu Wenruo
2025-10-20 9:46 ` Christoph Hellwig [this message]
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=aPYFECiBrh36AwtB@infradead.org \
--to=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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 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.