[moderation] [xfs?] general protection fault in xfs_trans_brelse

0 views
Skip to first unread message

syzbot

unread,
12:31 AM (3 hours ago) 12:31 AM
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 4539944e5151 Merge tag 'liveupdate-fixes-2026-07-22' of gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12a0e09e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=20c9876b0f77b546
dashboard link: https://syzkaller.appspot.com/bug?extid=665051d8569dadf344f4
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
CC: [c...@kernel.org linux-...@vger.kernel.org linu...@vger.kernel.org]

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-4539944e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e51f8eeaf728/vmlinux-4539944e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/349b7118aa67/bzImage-4539944e.xz

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

loop0: detected capacity change from 0 to 32768
=======================================================
WARNING: The mand mount option has been deprecated and
and is ignored by this kernel. Remove the mand
option from the mount to silence this warning.
=======================================================
XFS (loop0): Mounting V5 Filesystem bfdc47fc-10d8-4eed-a562-11a831b3f791
XFS (loop0): Ending clean mount
XFS (loop0): Quotacheck needed: Please wait.
XFS (loop0): Quotacheck: Done.
loop0: detected capacity change from 32768 to 0
XFS (loop0): metadata I/O error in "xfs_btree_read_buf_block+0x2ae/0x4a0" at daddr 0x18 len 4 error 5
XFS (loop0): metadata I/O error in "xfs_btree_read_buf_block+0x2ae/0x4a0" at daddr 0x18 len 4 error 5
XFS (loop0): metadata I/O error in "xfs_btree_read_buf_block+0x2ae/0x4a0" at daddr 0x18 len 4 error 5
XFS (loop0): metadata I/O error in "xfs_btree_read_buf_block+0x2ae/0x4a0" at daddr 0x18 len 4 error 5
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000014: 0000 [#1] SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x00000000000000a0-0x00000000000000a7]
CPU: 0 UID: 0 PID: 5318 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:xfs_trans_brelse+0xf6/0x3e0 fs/xfs/xfs_trans_buf.c:350
Code: e8 3f e9 ee ff 48 89 df 5b 41 5c 41 5d 41 5e 41 5f 5d e9 5d d1 ee ff e8 18 7f 22 fe 4d 8d be a4 00 00 00 4d 89 fd 49 c1 ed 03 <43> 0f b6 44 25 00 84 c0 0f 85 34 01 00 00 41 8b 2f 31 ff 89 ee e8
RSP: 0018:ffffc9000f8a7588 EFLAGS: 00010207
RAX: ffffffff83a40292 RBX: ffff8880131f7200 RCX: 0000000000100000
RDX: ffffc9000ef69000 RSI: 00000000000072ac RDI: 00000000000072ad
RBP: ffff888012817e01 R08: ffffffff9057adf7 R09: 1ffffffff20af5be
R10: dffffc0000000000 R11: fffffbfff20af5bf R12: dffffc0000000000
R13: 0000000000000014 R14: 0000000000000000 R15: 00000000000000a4
FS: 00007ff76abe56c0(0000) GS:ffff88808c549000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb572d9e94b CR3: 000000001fd40000 CR4: 0000000000352ef0
Call Trace:
<TASK>
xchk_ag_free+0x8a/0x180 fs/xfs/scrub/common.c:681
xchk_teardown+0x33/0x810 fs/xfs/scrub/scrub.c:232
xfs_scrub_metadata+0x13b2/0x1910 fs/xfs/scrub/scrub.c:766
xfs_ioc_scrubv_metadata+0x7ac/0xb70 fs/xfs/scrub/scrub.c:981
xfs_file_ioctl+0x916/0x1590 fs/xfs/xfs_ioctl.c:1308
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff769d9de99
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff76abe4fe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ff76a025fa0 RCX: 00007ff769d9de99
RDX: 0000200000000000 RSI: 00000000c0285840 RDI: 0000000000000006
RBP: 00007ff769e33eaf R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff76a026038 R14: 00007ff76a025fa0 R15: 00007ffe6316bce8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:xfs_trans_brelse+0xf6/0x3e0 fs/xfs/xfs_trans_buf.c:350
Code: e8 3f e9 ee ff 48 89 df 5b 41 5c 41 5d 41 5e 41 5f 5d e9 5d d1 ee ff e8 18 7f 22 fe 4d 8d be a4 00 00 00 4d 89 fd 49 c1 ed 03 <43> 0f b6 44 25 00 84 c0 0f 85 34 01 00 00 41 8b 2f 31 ff 89 ee e8
RSP: 0018:ffffc9000f8a7588 EFLAGS: 00010207
RAX: ffffffff83a40292 RBX: ffff8880131f7200 RCX: 0000000000100000
RDX: ffffc9000ef69000 RSI: 00000000000072ac RDI: 00000000000072ad
RBP: ffff888012817e01 R08: ffffffff9057adf7 R09: 1ffffffff20af5be
R10: dffffc0000000000 R11: fffffbfff20af5bf R12: dffffc0000000000
R13: 0000000000000014 R14: 0000000000000000 R15: 00000000000000a4
FS: 00007ff76abe56c0(0000) GS:ffff88808c549000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff76a014ca0 CR3: 000000001fd40000 CR4: 0000000000352ef0
----------------
Code disassembly (best guess):
0: e8 3f e9 ee ff call 0xffeee944
5: 48 89 df mov %rbx,%rdi
8: 5b pop %rbx
9: 41 5c pop %r12
b: 41 5d pop %r13
d: 41 5e pop %r14
f: 41 5f pop %r15
11: 5d pop %rbp
12: e9 5d d1 ee ff jmp 0xffeed174
17: e8 18 7f 22 fe call 0xfe227f34
1c: 4d 8d be a4 00 00 00 lea 0xa4(%r14),%r15
23: 4d 89 fd mov %r15,%r13
26: 49 c1 ed 03 shr $0x3,%r13
* 2a: 43 0f b6 44 25 00 movzbl 0x0(%r13,%r12,1),%eax <-- trapping instruction
30: 84 c0 test %al,%al
32: 0f 85 34 01 00 00 jne 0x16c
38: 41 8b 2f mov (%r15),%ebp
3b: 31 ff xor %edi,%edi
3d: 89 ee mov %ebp,%esi
3f: e8 .byte 0xe8


---
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
Reply all
Reply to author
Forward
0 new messages