Hello, syzbot found the following issue on: HEAD commit: 58390c8ce1bd Merge tag 'iommu-updates-v6.4' of git://git.k.. git tree: upstream console+strace: https://syzkaller.appspot.com/x/log.txt?x=136e6ef8280000 kernel config: https://syzkaller.appspot.com/x/.config?x=5eadbf0d3c2ece89 dashboard link: https://syzkaller.appspot.com/bug?extid=eb6201248f684e99b9f8 compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16bbb03c280000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=140d36f8280000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/60130779f509/disk-58390c8c.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/d7f0cdd29b71/vmlinux-58390c8c.xz kernel image: https://storage.googleapis.com/syzbot-assets/de415ad52ae4/bzImage-58390c8c.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/dc89d01cd6e9/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+eb6201248f684e99b9f8@xxxxxxxxxxxxxxxxxxxxxxxxx syz-executor768: attempt to access beyond end of device loop0: rw=2049, sector=77824, nr_sectors = 2048 limit=63271 syz-executor768: attempt to access beyond end of device loop0: rw=2049, sector=79872, nr_sectors = 2048 limit=63271 ================================================ WARNING: lock held when returning to user space! 6.3.0-syzkaller-12049-g58390c8ce1bd #0 Not tainted ------------------------------------------------ syz-executor768/4998 is leaving the kernel with locks still held! 1 lock held by syz-executor768/4998: #0: ffff88807e800448 (&sbi->node_write){++++}-{3:3}, at: f2fs_down_read fs/f2fs/f2fs.h:2087 [inline] #0: ffff88807e800448 (&sbi->node_write){++++}-{3:3}, at: f2fs_write_single_data_page+0xa10/0x1d50 fs/f2fs/data.c:2842 --- 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 syzkaller@xxxxxxxxxxxxxxxx. 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 syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. 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
