Hello,
syzbot found the following issue on:
HEAD commit: 3b29299e5f60 Linux 6.1.22
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=139eb68dc80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=bbb9a1f6f7f5a1d9
dashboard link:
https://syzkaller.appspot.com/bug?extid=21835cb68f88c9a4cec4
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/2affbd06cbfd/disk-3b29299e.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/8b22d1baf827/vmlinux-3b29299e.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/d5e3891c88bf/Image-3b29299e.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+21835c...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/jfs/inode.c:169!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4362 Comm: syz-executor.5 Not tainted 6.1.22-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : jfs_evict_inode+0x3b0/0x3f4 fs/jfs/inode.c:169
lr : jfs_evict_inode+0x3b0/0x3f4 fs/jfs/inode.c:169
sp : ffff80001dc77710
x29: ffff80001dc77710 x28: 1fffe0001c0398d7 x27: dfff800000000000
x26: 1fffe0001c0398d5 x25: 1fffe0001c0398a3 x24: ffff8000125871c0
x23: dfff800000000000 x22: ffff0000e01cc5c8 x21: ffff0000e01cc6a8
x20: ffff0000e01cc178 x19: ffff0000e01cc4f0 x18: ffff80001dc76c00
x17: ffff80001557d000 x16: ffff80000825e1ac x15: 0000000000000000
x14: 1ffff00002ab00b0 x13: dfff800000000000 x12: 0000000000000003
x11: ff8080000994f71c x10: 0000000000000000 x9 : ffff80000994f71c
x8 : ffff0000cd44b680 x7 : ffff800008a9c15c x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000006 x1 : 0000000000000000 x0 : ffff0000e01cc4d0
Call trace:
jfs_evict_inode+0x3b0/0x3f4 fs/jfs/inode.c:169
evict+0x260/0x68c fs/inode.c:664
dispose_list fs/inode.c:697 [inline]
evict_inodes+0x6b4/0x74c fs/inode.c:747
generic_shutdown_super+0x9c/0x328 fs/super.c:480
kill_block_super+0x70/0xdc fs/super.c:1450
deactivate_locked_super+0xac/0x124 fs/super.c:332
deactivate_super+0xf0/0x110 fs/super.c:363
cleanup_mnt+0x394/0x41c fs/namespace.c:1186
__cleanup_mnt+0x20/0x30 fs/namespace.c:1193
task_work_run+0x240/0x2f0 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
do_notify_resume+0x2144/0x3470 arch/arm64/kernel/signal.c:1132
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]
el0_svc+0x9c/0x168 arch/arm64/kernel/entry-common.c:638
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
Code: aa1603e1 944c912b 17ffff77 97ae9e6e (d4210000)
---[ 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.