[syzbot] [f2fs?] kernel BUG in f2fs_evict_inode (4)

12 views
Skip to first unread message

syzbot

unread,
Nov 16, 2024, 7:19:26 AM11/16/24
to ch...@kernel.org, jae...@kernel.org, linux-f2...@lists.sourceforge.net, linux-...@vger.kernel.org, syzkall...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 2d5404caa8c7 Linux 6.12-rc7
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=108a0ce8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1503500c6f615d24
dashboard link: https://syzkaller.appspot.com/bug?extid=5c81eb8c0a380fa578b5
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/a2d329b82126/disk-2d5404ca.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/37a04ca225dd/vmlinux-2d5404ca.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4f837ce9d9dc/bzImage-2d5404ca.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5c81eb...@syzkaller.appspotmail.com

------------[ cut here ]------------
kernel BUG at fs/f2fs/inode.c:901!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 1 UID: 0 PID: 6239 Comm: syz-executor Not tainted 6.12.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:901
Code: 2e 8b a5 fd 31 ff 89 de e8 25 8b a5 fd 40 84 ed 75 28 e8 1b 88 a5 fd e9 3c ec ff ff e8 11 88 a5 fd 90 0f 0b e8 09 88 a5 fd 90 <0f> 0b e8 01 88 a5 fd 90 0f 0b 90 e9 fc fe ff ff e8 f3 87 a5 fd e8
RSP: 0000:ffffc9000529f928 EFLAGS: 00010293
RAX: ffffffff83ef51a7 RBX: 0000000000000002 RCX: ffff8880312a1e00
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff83ef4b90 R09: 1ffff1100c3aeed9
R10: dffffc0000000000 R11: ffffed100c3aeeda R12: ffff888027a68000
R13: ffff888061d776c8 R14: ffff888061d77228 R15: dffffc0000000000
FS: 000055556b022500(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcb2134e000 CR3: 0000000061454000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
evict+0x4e8/0x9b0 fs/inode.c:725
dispose_list fs/inode.c:774 [inline]
evict_inodes+0x6f6/0x790 fs/inode.c:828
generic_shutdown_super+0xa0/0x2d0 fs/super.c:627
kill_block_super+0x44/0x90 fs/super.c:1710
kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4927
deactivate_locked_super+0xc4/0x130 fs/super.c:473
cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373
task_work_run+0x24f/0x310 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0x168/0x370 kernel/entry/common.c:218
do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f34b5b7fa47
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007fff051bb088 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f34b5b7fa47
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fff051bb140
RBP: 00007fff051bb140 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fff051bc1c0
R13: 00007f34b5bf14b4 R14: 000000000002dc8b R15: 00007fff051bc200
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:901
Code: 2e 8b a5 fd 31 ff 89 de e8 25 8b a5 fd 40 84 ed 75 28 e8 1b 88 a5 fd e9 3c ec ff ff e8 11 88 a5 fd 90 0f 0b e8 09 88 a5 fd 90 <0f> 0b e8 01 88 a5 fd 90 0f 0b 90 e9 fc fe ff ff e8 f3 87 a5 fd e8
RSP: 0000:ffffc9000529f928 EFLAGS: 00010293

RAX: ffffffff83ef51a7 RBX: 0000000000000002 RCX: ffff8880312a1e00
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff83ef4b90 R09: 1ffff1100c3aeed9
R10: dffffc0000000000 R11: ffffed100c3aeeda R12: ffff888027a68000
R13: ffff888061d776c8 R14: ffff888061d77228 R15: dffffc0000000000
FS: 000055556b022500(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f00031ff800 CR3: 0000000061454000 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 syzk...@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

syzbot

unread,
Dec 6, 2024, 12:07:34 PM12/6/24
to ch...@kernel.org, jae...@kernel.org, linux-f2...@lists.sourceforge.net, linux-...@vger.kernel.org, syzkall...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: b8f52214c61a Merge tag 'audit-pr-20241205' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12ba98df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=335e39020523e2ed
dashboard link: https://syzkaller.appspot.com/bug?extid=5c81eb8c0a380fa578b5
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155bd0f8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13cad330580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cfa353b9a35b/disk-b8f52214.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4e744ff2abaf/vmlinux-b8f52214.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2dbf687d48e1/bzImage-b8f52214.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/45ab44aae0f6/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5c81eb...@syzkaller.appspotmail.com

------------[ cut here ]------------
kernel BUG at fs/f2fs/inode.c:920!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 1 UID: 0 PID: 5827 Comm: syz-executor120 Not tainted 6.13.0-rc1-syzkaller-00182-gb8f52214c61a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:f2fs_evict_inode+0x1671/0x1690 fs/f2fs/inode.c:920
Code: 31 ff 89 de e8 f0 f0 a3 fd 40 84 ed 75 2c e8 e6 ed a3 fd 4c 8b 3c 24 e9 63 eb ff ff e8 d8 ed a3 fd 90 0f 0b e8 d0 ed a3 fd 90 <0f> 0b e8 c8 ed a3 fd 90 0f 0b 90 e9 fb fe ff ff e8 ba ed a3 fd e8
RSP: 0018:ffffc90003d17918 EFLAGS: 00010293
RAX: ffffffff83fb83f0 RBX: 0000000000000002 RCX: ffff88804cda8000
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff83fb7dd7 R09: 1ffff1100cbe51ad
R10: dffffc0000000000 R11: ffffed100cbe51ae R12: ffff888065f28910
R13: ffff888065f288c8 R14: dffffc0000000000 R15: ffff88807e0e0000
FS: 00005555814413c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2787dbd000 CR3: 0000000021b7c000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
evict+0x4e8/0x9a0 fs/inode.c:796
dispose_list fs/inode.c:845 [inline]
evict_inodes+0x6f6/0x790 fs/inode.c:899
generic_shutdown_super+0xa0/0x2d0 fs/super.c:627
kill_block_super+0x44/0x90 fs/super.c:1710
kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4972
deactivate_locked_super+0xc4/0x130 fs/super.c:473
cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373
task_work_run+0x24f/0x310 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0x13f/0x340 kernel/entry/common.c:218
do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f278ef02cb7
Code: 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b0 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffca034a6e8 EFLAGS: 00000206 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f278ef02cb7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffca034a7a0
RBP: 00007ffca034a7a0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000206 R12: 00007ffca034b850
R13: 0000555581442700 R14: 0000000000016846 R15: 0000000000000008
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:f2fs_evict_inode+0x1671/0x1690 fs/f2fs/inode.c:920
Code: 31 ff 89 de e8 f0 f0 a3 fd 40 84 ed 75 2c e8 e6 ed a3 fd 4c 8b 3c 24 e9 63 eb ff ff e8 d8 ed a3 fd 90 0f 0b e8 d0 ed a3 fd 90 <0f> 0b e8 c8 ed a3 fd 90 0f 0b 90 e9 fb fe ff ff e8 ba ed a3 fd e8
RSP: 0018:ffffc90003d17918 EFLAGS: 00010293
RAX: ffffffff83fb83f0 RBX: 0000000000000002 RCX: ffff88804cda8000
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff83fb7dd7 R09: 1ffff1100cbe51ad
R10: dffffc0000000000 R11: ffffed100cbe51ae R12: ffff888065f28910
R13: ffff888065f288c8 R14: dffffc0000000000 R15: ffff88807e0e0000
FS: 00005555814413c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2787dbd000 CR3: 0000000021b7c000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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.

syzbot

unread,
Dec 7, 2024, 5:59:04 PM12/7/24
to ch...@kernel.org, dro...@google.com, jae...@kernel.org, linux-f2...@lists.sourceforge.net, linux-...@vger.kernel.org, syzkall...@googlegroups.com
syzbot has bisected this issue to:

commit acff9409dd40beaca2bd982678d222e2740ad84b
Author: Jaegeuk Kim <jae...@kernel.org>
Date: Tue Nov 12 01:04:58 2024 +0000

Revert "f2fs: remove unreachable lazytime mount option parsing"

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=130903e8580000
start commit: b8f52214c61a Merge tag 'audit-pr-20241205' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=108903e8580000
console output: https://syzkaller.appspot.com/x/log.txt?x=170903e8580000
Reported-by: syzbot+5c81eb...@syzkaller.appspotmail.com
Fixes: acff9409dd40 ("Revert "f2fs: remove unreachable lazytime mount option parsing"")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages