#syz test: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/common
On 4/2/25 08:00, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: 4e82c87058f4 Merge tag 'rust-6.15' of git://git.kernel.org.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=17007198580000 > kernel config: https://syzkaller.appspot.com/x/.config?x=4253e469c0d32ef6 > dashboard link: https://syzkaller.appspot.com/bug?extid=803dd716c4310d16ff3a > compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) > 2.40 > > Unfortunately, I don't have any reproducer for this issue yet. > > Downloadable assets: > disk image: > https://storage.googleapis.com/syzbot-assets/5e6f1c2744e3/disk-4e82c870.raw.xz > vmlinux: > https://storage.googleapis.com/syzbot-assets/5c1a60744d62/vmlinux-4e82c870.xz > kernel image: > https://storage.googleapis.com/syzbot-assets/228bbd75bd12/bzImage-4e82c870.xz > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+803dd716c4310d16f...@syzkaller.appspotmail.com > > ------------[ cut here ]------------ > kernel BUG at fs/f2fs/data.c:358! > Oops: invalid opcode: 0000 [#1] SMP KASAN PTI > CPU: 1 UID: 0 PID: 23 Comm: ksoftirqd/1 Not tainted > 6.14.0-syzkaller-10892-g4e82c87058f4 #0 PREEMPT(full) > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS > Google 02/12/2025 > RIP: 0010:f2fs_write_end_io+0x77a/0x790 fs/f2fs/data.c:357 > Code: e8 8b 01 f2 fd e9 a2 fa ff ff 89 d9 80 e1 07 38 c1 0f 8c fe fa ff ff 48 > 89 df e8 11 01 f2 fd e9 f1 fa ff ff e8 87 92 8b fd 90 <0f> 0b e8 8f d4 ed 07 > 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 > RSP: 0018:ffffc900001d79c0 EFLAGS: 00010246 > RAX: ffffffff8437d9e9 RBX: 0000000000000000 RCX: ffff88801da85a00 > RDX: 0000000000000100 RSI: 0000000000000000 RDI: 000000000000000a > RBP: ffffc900001d7ac8 R08: ffffffff8437d696 R09: 1ffffd400012b785 > R10: dffffc0000000000 R11: fffff9400012b786 R12: 0000000000000001 > R13: dffffc0000000000 R14: 000000000000000a R15: ffffea000095bc00 > FS: 0000000000000000(0000) GS:ffff8881250e5000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 00007fd1b21f9438 CR3: 000000007b684000 CR4: 00000000003526f0 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > Call Trace: > <TASK> > blk_update_request+0x5e5/0x1160 block/blk-mq.c:983 > blk_mq_end_request+0x3e/0x70 block/blk-mq.c:1145 > blk_complete_reqs block/blk-mq.c:1220 [inline] > blk_done_softirq+0x100/0x150 block/blk-mq.c:1225 > handle_softirqs+0x2d6/0x9b0 kernel/softirq.c:579 > run_ksoftirqd+0xcf/0x130 kernel/softirq.c:968 > smpboot_thread_fn+0x576/0xaa0 kernel/smpboot.c:164 > kthread+0x7b7/0x940 kernel/kthread.c:464 > ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:153 > ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 > </TASK> > Modules linked in: > ---[ end trace 0000000000000000 ]--- > RIP: 0010:f2fs_write_end_io+0x77a/0x790 fs/f2fs/data.c:357 > Code: e8 8b 01 f2 fd e9 a2 fa ff ff 89 d9 80 e1 07 38 c1 0f 8c fe fa ff ff 48 > 89 df e8 11 01 f2 fd e9 f1 fa ff ff e8 87 92 8b fd 90 <0f> 0b e8 8f d4 ed 07 > 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 > RSP: 0018:ffffc900001d79c0 EFLAGS: 00010246 > RAX: ffffffff8437d9e9 RBX: 0000000000000000 RCX: ffff88801da85a00 > RDX: 0000000000000100 RSI: 0000000000000000 RDI: 000000000000000a > RBP: ffffc900001d7ac8 R08: ffffffff8437d696 R09: 1ffffd400012b785 > R10: dffffc0000000000 R11: fffff9400012b786 R12: 0000000000000001 > R13: dffffc0000000000 R14: 000000000000000a R15: ffffea000095bc00 > FS: 0000000000000000(0000) GS:ffff8881250e5000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 00007fd1b21f9438 CR3: 000000007b684000 CR4: 00000000003526f0 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > > > --- > 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 syzkal...@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 _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
