Hello,
syzbot found the following issue on:
HEAD commit: ca87e77a2ef8 Linux 6.1.34
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=15f412f3280000
kernel config:
https://syzkaller.appspot.com/x/.config?x=143044f84cdceac2
dashboard link:
https://syzkaller.appspot.com/bug?extid=17b1d6e43bf67dcfc9c7
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/1141c37ce351/disk-ca87e77a.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/de1fca0d0bb4/vmlinux-ca87e77a.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/c3417b70e0bf/Image-ca87e77a.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+17b1d6...@syzkaller.appspotmail.com
gfs2: fsid=loop3.0: first mount done, others may mount
------------[ cut here ]------------
WARNING: CPU: 0 PID: 2277 at fs/gfs2/rgrp.c:2628 gfs2_check_blk_type+0x394/0x598
Modules linked in:
CPU: 0 PID: 2277 Comm: syz-executor.3 Not tainted 6.1.34-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : gfs2_check_blk_type+0x394/0x598
lr : rgrp_contains_block fs/gfs2/rgrp.h:88 [inline]
lr : gfs2_rbm_from_block fs/gfs2/rgrp.c:279 [inline]
lr : gfs2_check_blk_type+0x310/0x598 fs/gfs2/rgrp.c:2627
sp : ffff80001ea976c0
x29: ffff80001ea97780 x28: ffff0000c387c660 x27: dfff800000000000
x26: ffff700003d52edc x25: ffff80001ea97700 x24: 0000000000000013
x23: ffff0000c387c694 x22: 00000000fffffff9 x21: 0000000000000012
x20: 1fffe0001870f8d2 x19: 1fffe0001870f8d1 x18: 1fffe000368b5f76
x17: ffff8000155bd000 x16: ffff8000082dbeb8 x15: ffff0001b45afbbc
x14: 1ffff00002ab80b0 x13: dfff800000000000 x12: 0000000000040000
x11: 0000000000003ab3 x10: ffff8000296cf000 x9 : ffff80000a3d5984
x8 : 0000000000003ab4 x7 : ffff80000827cdcc x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : ffff80000a36becc
x2 : 0000000000000001 x1 : 0000000000000012 x0 : 0000000000000013
Call trace:
gfs2_check_blk_type+0x394/0x598
gfs2_inode_lookup+0x980/0xbac fs/gfs2/inode.c:173
gfs2_lookup_by_inum+0x60/0xf8 fs/gfs2/inode.c:241
gfs2_get_dentry fs/gfs2/export.c:139 [inline]
gfs2_fh_to_dentry+0x128/0x1f4 fs/gfs2/export.c:162
exportfs_decode_fh_raw+0x114/0x4b4 fs/exportfs/expfs.c:435
exportfs_decode_fh+0x50/0x80 fs/exportfs/expfs.c:575
do_handle_to_path fs/fhandle.c:152 [inline]
handle_to_path fs/fhandle.c:207 [inline]
do_handle_open+0x56c/0x998 fs/fhandle.c:223
__do_sys_open_by_handle_at fs/fhandle.c:265 [inline]
__se_sys_open_by_handle_at fs/fhandle.c:256 [inline]
__arm64_sys_open_by_handle_at+0x80/0x94 fs/fhandle.c:256
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 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:581
irq event stamp: 138116
hardirqs last enabled at (138115): [<ffff80000827ce6c>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1367 [inline]
hardirqs last enabled at (138115): [<ffff80000827ce6c>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:5000
hardirqs last disabled at (138116): [<ffff800012101f6c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (138062): [<ffff80000a377a74>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (138060): [<ffff80000a377a40>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---
---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup