From: "Darrick J. Wong" <djwong@kernel.org>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: [6.15-rc2 regression] xfs: null pointer in the dax fault code
Date: Wed, 16 Apr 2025 10:43:58 -0700 [thread overview]
Message-ID: <20250416174358.GM25675@frogsfrogsfrogs> (raw)
Hi folks,
After upgrading to 6.15-rc2, I see the following crash in (I think?) the
DAX code on xfs/593 (which is a fairly boring fsck test).
MKFS_OPTIONS=" -m metadir=1,autofsck=1,uquota,gquota,pquota, -d daxinherit=1,"
MOUNT_OPTIONS=""
Any ideas? Does this stack trace ring a bell for anyone?
--D
BUG: kernel NULL pointer dereference, address: 00000000000008a8
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 0 P4D 0
Oops: Oops: 0000 [#1] SMP
CPU: 2 UID: 0 PID: 1717921 Comm: fsstress Tainted: G W 6.15.0-rc2-xfsx #rc2 PREEMPT(lazy)
Tainted: [W]=WARN
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:__lruvec_stat_mod_folio+0x50/0xd0
Code: e8 85 70 da ff 48 8b 53 38 48 89 d0 48 83 e0 f8 83 e2 02 74 04 48 8b 40 10 48 63 d5 48 85 c0 74 50 6
0 75 54 44
RSP: 0000:ffffc9000679fa20 EFLAGS: 00010206
RAX: 0000000000000200 RBX: ffffea000e298040 RCX: 0000000000000001
RDX: 0000000000000001 RSI: 0000000000000012 RDI: ffffea000e298040
RBP: 0000000000000001 R08: 8000000000000025 R09: 0000000000000001
R10: 0000000000001000 R11: ffffc9000679fc10 R12: 0000000000000012
R13: ffff88807ffd9d80 R14: ffff888040a79a80 R15: ffffea000e298040
FS: 00007f2dce659740(0000) GS:ffff8880fb85e000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000000008a8 CR3: 000000005f22a003 CR4: 00000000001706f0
Call Trace:
<TASK>
folio_add_file_rmap_ptes+0x109/0x200
insert_page_into_pte_locked+0x1b6/0x340
insert_page+0x93/0xc0
vmf_insert_page_mkwrite+0x2d/0x50
dax_fault_iter+0x330/0x730
dax_iomap_pte_fault+0x1a9/0x3e0
__xfs_write_fault+0x11d/0x290 [xfs 05d1f477986dfc3e3925c4fd18979e6f6f9a9e35]
__do_fault+0x2d/0x170
do_fault+0xc8/0x680
__handle_mm_fault+0x5ba/0x1030
handle_mm_fault+0x18f/0x280
do_user_addr_fault+0x481/0x7e0
exc_page_fault+0x62/0x130
asm_exc_page_fault+0x22/0x30
RIP: 0033:0x7f2dce7af44a
Code: c5 fe 7f 07 c5 fe 7f 47 20 c5 fe 7f 47 40 c5 fe 7f 47 60 c5 f8 77 c3 66 0f 1f 84 00 00 00 00 00 40 0
0 00 66 90
RSP: 002b:00007fffe75b3198 EFLAGS: 00010202
RAX: 0000000000000054 RBX: 000000000008c000 RCX: 0000000000000dfd
RDX: 00007f2dce63e000 RSI: 0000000000000054 RDI: 00007f2dce658000
RBP: 000000000001adfd R08: 0000000000000005 R09: 000000000008c000
R10: 0000000000000008 R11: 0000000000000246 R12: 00007fffe75b31e0
R13: 8f5c28f5c28f5c29 R14: 00007fffe75b37a0 R15: 000056030c3be570
</TASK>
Modules linked in: ext4 crc16 mbcache jbd2 xfs nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv
set_hash_ip ip_set_hash_net xt_set nft_compat ip_set_hash_mac ip_set nf_tables nfnetlink sha512_ssse3 ahci
d_btt sch_fq_codel loop fuse configfs ip_tables x_tables overlay nfsv4 af_packet
Dumping ftrace buffer:
(ftrace buffer empty)
CR2: 00000000000008a8
---[ end trace 0000000000000000 ]---
next reply other threads:[~2025-04-16 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 17:43 Darrick J. Wong [this message]
2025-04-16 20:22 ` [6.15-rc2 regression] xfs: null pointer in the dax fault code Darrick J. Wong
2025-04-16 20:50 ` Dave Chinner
2025-04-17 3:01 ` Darrick J. Wong
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=20250416174358.GM25675@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox