[v6.1] BUG: unable to handle kernel paging request in trace_event_raw_event_btrfs__inode

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cf82dcca9634 Linux 6.1.187
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15a09901580000
kernel config: https://syzkaller.appspot.com/x/.config?x=872c04466179833f
dashboard link: https://syzkaller.appspot.com/bug?extid=b214c9e17082996ca04f
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/425a730ba33a/disk-cf82dcca.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7dd95cb647d8/vmlinux-cf82dcca.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b21aedea13f/Image-cf82dcca.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b214c9...@syzkaller.appspotmail.com

BTRFS info (device loop0): enabling ssd optimizations
BTRFS info (device loop0): setting compat-ro feature flag for VERITY (0x4)
Unable to handle kernel paging request at virtual address dfff80000000003e
KASAN: null-ptr-deref in range [0x00000000000001f0-0x00000000000001f7]
Mem abort info:
ESR = 0x0000000096000006
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
Data abort info:
ISV = 0, ISS = 0x00000006
CM = 0, WnR = 0
[dfff80000000003e] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 6643 Comm: syz.0.662 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/07/2026
pstate: 62400005 (nZCv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : do_trace_event_raw_event_btrfs__inode include/trace/events/btrfs.h:229 [inline]
pc : trace_event_raw_event_btrfs__inode+0x2f0/0x3f8 include/trace/events/btrfs.h:205
lr : do_trace_event_raw_event_btrfs__inode include/trace/events/btrfs.h:221 [inline]
lr : trace_event_raw_event_btrfs__inode+0x158/0x3f8 include/trace/events/btrfs.h:205
sp : ffff800021247640
x29: ffff8000212476d0 x28: dfff800000000000 x27: ffff700004248ef4
x26: 0000000000000000 x25: ffff0000d2f9377c x24: dfff800000000000
x23: ffff800021247640 x22: ffff700004248ec8 x21: 0000000000000000
x20: ffff0000d2f9373c x19: 00000000000001f7 x18: 1fffe00033e6df7e
x17: ffff80001539d000 x16: ffff8000082f2d54 x15: 0000000000000002
x14: 0000000000000003 x13: 5d3eb9a580cd6d81 x12: 7c477e297af65e39
x11: 0000000000000000 x10: ffff60001a5f26eb x9 : 0000000000000000
x8 : 000000000000003e x7 : 5d3eb9a580cd6d81 x6 : 7c477e297af65e39
x5 : ffff0000d2f93754 x4 : ffff0000f5accc10 x3 : ffff800009f71c10
x2 : 0000000000000010 x1 : ffff0000f5accc00 x0 : 00000000000001fe
Call trace:
do_trace_event_raw_event_btrfs__inode include/trace/events/btrfs.h:229 [inline]
trace_event_raw_event_btrfs__inode+0x2f0/0x3f8 include/trace/events/btrfs.h:205
__traceiter_btrfs_inode_evict+0x74/0xc8 include/trace/events/btrfs.h:257
trace_btrfs_inode_evict include/trace/events/btrfs.h:257 [inline]
btrfs_evict_inode+0xb94/0xc7c fs/btrfs/inode.c:5541
evict+0x3d8/0x824 fs/inode.c:705
iput_final fs/inode.c:1834 [inline]
iput+0x728/0x7e8 fs/inode.c:1860
btrfs_create_common+0x1cc/0x240 fs/btrfs/inode.c:6876
btrfs_mkdir+0xcc/0xf0 fs/btrfs/inode.c:7004
vfs_mkdir+0x314/0x4d8 fs/namei.c:4157
do_mkdirat+0x1b8/0x3ec fs/namei.c:4182
__do_sys_mkdirat fs/namei.c:4197 [inline]
__se_sys_mkdirat fs/namei.c:4195 [inline]
__arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4195
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x200/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: f9400269 9107dd33 9107f920 d343fe68 (38f86908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: f9400269 ldr x9, [x19]
4: 9107dd33 add x19, x9, #0x1f7
8: 9107f920 add x0, x9, #0x1fe
c: d343fe68 lsr x8, x19, #3
* 10: 38f86908 ldrsb w8, [x8, x24] <-- trapping instruction


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup