kernel BUG at fs/f2fs/inode.c:LINE!

14 views
Skip to first unread message

syzbot

unread,
Oct 13, 2020, 12:23:16 AM10/13/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: a1b977b4 Linux 4.19.150
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=172e5f00500000
kernel config: https://syzkaller.appspot.com/x/.config?x=c14008c8da1ca4d4
dashboard link: https://syzkaller.appspot.com/bug?extid=1f29dfb52bc47a05075f
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10383a10500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1702d8f7900000

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

F2FS-fs (loop0): Can't find valid F2FS filesystem in 2th superblock
F2FS-fs (loop0): invalid crc value
F2FS-fs (loop0): f2fs_check_nid_range: out-of-range nid=1, run fsck to fix.
F2FS-fs (loop0): f2fs_check_nid_range: out-of-range nid=2, run fsck to fix.
------------[ cut here ]------------
kernel BUG at fs/f2fs/inode.c:706!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 6497 Comm: syz-executor878 Not tainted 4.19.150-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:f2fs_evict_inode+0x10a1/0x1380 fs/f2fs/inode.c:706
Code: de e8 13 b0 3f fe 85 db 0f 84 1a ff ff ff e9 08 ff ff ff e8 91 ae 3f fe 48 89 ef e8 e9 6d 03 00 e9 dd f3 ff ff e8 7f ae 3f fe <0f> 0b 48 c7 c7 e0 36 f1 89 e8 41 f8 83 00 4c 89 f7 e8 69 fd 78 fe
RSP: 0018:ffff88808b5d7940 EFLAGS: 00010293
RAX: ffff8880a428e440 RBX: 0000000000000001 RCX: ffffffff833217b0
RDX: 0000000000000000 RSI: ffffffff833223e1 RDI: 0000000000000007
RBP: ffff8880800470c0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000007 R11: 00000000000005c9 R12: ffff8880a3ab9040
R13: ffff888080047490 R14: dffffc0000000000 R15: ffff8880a3ab9ee4
FS: 0000000000d94880(0000) GS:ffff8880ae300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055a0f4c64750 CR3: 000000008fd80000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
evict+0x2ed/0x780 fs/inode.c:559
iput_final fs/inode.c:1555 [inline]
iput+0x511/0x890 fs/inode.c:1581
f2fs_fill_super+0x5b26/0x7920 fs/f2fs/super.c:3064
mount_bdev+0x2fc/0x3b0 fs/super.c:1158
mount_fs+0xa3/0x318 fs/super.c:1261
vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961
vfs_kern_mount fs/namespace.c:951 [inline]
do_new_mount fs/namespace.c:2469 [inline]
do_mount+0x51c/0x2f10 fs/namespace.c:2799
ksys_mount+0xcf/0x130 fs/namespace.c:3015
__do_sys_mount fs/namespace.c:3029 [inline]
__se_sys_mount fs/namespace.c:3026 [inline]
__x64_sys_mount+0xba/0x150 fs/namespace.c:3026
do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x44703a
Code: b8 08 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 fd ad fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 da ad fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007ffd403e1128 EFLAGS: 00000297 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffd403e1180 RCX: 000000000044703a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffd403e1140
RBP: 00007ffd403e1140 R08: 00007ffd403e1180 R09: 00007ffd00000015
R10: 0000000000000000 R11: 0000000000000297 R12: 0000000000000008
R13: 0000000000000004 R14: 0000000000000003 R15: 0000000000000003
Modules linked in:
---[ end trace 59dc4f5a4e8716c6 ]---
RIP: 0010:f2fs_evict_inode+0x10a1/0x1380 fs/f2fs/inode.c:706
Code: de e8 13 b0 3f fe 85 db 0f 84 1a ff ff ff e9 08 ff ff ff e8 91 ae 3f fe 48 89 ef e8 e9 6d 03 00 e9 dd f3 ff ff e8 7f ae 3f fe <0f> 0b 48 c7 c7 e0 36 f1 89 e8 41 f8 83 00 4c 89 f7 e8 69 fd 78 fe
RSP: 0018:ffff88808b5d7940 EFLAGS: 00010293
RAX: ffff8880a428e440 RBX: 0000000000000001 RCX: ffffffff833217b0
RDX: 0000000000000000 RSI: ffffffff833223e1 RDI: 0000000000000007
RBP: ffff8880800470c0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000007 R11: 00000000000005c9 R12: ffff8880a3ab9040
R13: ffff888080047490 R14: dffffc0000000000 R15: ffff8880a3ab9ee4
FS: 0000000000d94880(0000) GS:ffff8880ae300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055a0f4c64750 CR3: 000000008fd80000 CR4: 00000000001406e0
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages