Hello,
syzbot found the following issue on:
HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=137363bc880000
kernel config:
https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link:
https://syzkaller.appspot.com/bug?extid=6476a439e8b6cf0bef36
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=15823982880000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=14fdf55c880000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz
mounted in repro:
https://storage.googleapis.com/syzbot-assets/523d43539d8d/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+6476a4...@syzkaller.appspotmail.com
IPVS: ftp: loaded support on port[0] = 21
UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/09/12 12:00 (1000)
WARNING: CPU: 1 PID: 8087 at fs/udf/udfdecl.h:122 udf_updated_lvid fs/udf/udfdecl.h:122 [inline]
WARNING: CPU: 1 PID: 8087 at fs/udf/udfdecl.h:122 udf_free_inode+0x29b/0x320 fs/udf/ialloc.c:41
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 8087 Comm: syz-executor555 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:udf_updated_lvid fs/udf/udfdecl.h:122 [inline]
RIP: 0010:udf_free_inode+0x29b/0x320 fs/udf/ialloc.c:41
Code: 0f b6 14 02 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 04 84 d2 75 29 83 6d 24 01 e9 76 fe ff ff e8 3c 25 f4 fe 0f 0b e8 35 25 f4 fe <0f> 0b e9 4e ff ff ff 48 89 df e8 f6 00 2a ff e9 fc fd ff ff e8 7c
RSP: 0018:ffff8880b2f8fa58 EFLAGS: 00010293
RAX: ffff8880986ce3c0 RBX: ffff88808dbcfbc0 RCX: ffffffff826e5f87
RDX: 0000000000000000 RSI: ffffffff826e603b RDI: 0000000000000005
RBP: ffff8880af193040 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880b31ae2c0
R13: ffff8880af1930f8 R14: 0000000000000001 R15: ffff8880b31ae940
udf_evict_inode+0x350/0x590 fs/udf/inode.c:157
evict+0x2ed/0x760 fs/inode.c:559
iput_final fs/inode.c:1555 [inline]
iput+0x4f1/0x860 fs/inode.c:1581
udf_free_partition fs/udf/super.c:286 [inline]
udf_sb_free_partitions.isra.0+0x751/0xba0 fs/udf/super.c:317
udf_put_super+0x172/0x290 fs/udf/super.c:2363
generic_shutdown_super+0x144/0x370 fs/super.c:456
kill_block_super+0x97/0xf0 fs/super.c:1185
deactivate_locked_super+0x94/0x160 fs/super.c:329
deactivate_super+0x174/0x1a0 fs/super.c:360
cleanup_mnt+0x1a8/0x290 fs/namespace.c:1098
task_work_run+0x148/0x1c0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xbf3/0x2be0 kernel/exit.c:870
do_group_exit+0x125/0x310 kernel/exit.c:967
__do_sys_exit_group kernel/exit.c:978 [inline]
__se_sys_exit_group kernel/exit.c:976 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:976
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f9914494c59
Code: Bad RIP value.
RSP: 002b:00007fff9fbd6a98 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f991450b3f0 RCX: 00007f9914494c59
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 0000000000000001 R08: ffffffffffffffc0 R09: 00007f9914505e40
R10: 00007f9914505e40 R11: 0000000000000246 R12: 00007f991450b3f0
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches