From: Jaegeuk Kim <jaegeuk@kernel.org>
To: syzbot <syzbot+e1246909d526a9d470fa@syzkaller.appspotmail.com>
Cc: syzkaller-bugs@googlegroups.com, hughd@google.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, linux-mm@kvack.org,
akpm@linux-foundation.org
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] [tmpfs?] kernel BUG in f2fs_evict_inode
Date: Fri, 7 Jul 2023 07:20:11 -0700 [thread overview]
Message-ID: <ZKgfG5yE+VoMiVsZ@google.com> (raw)
In-Reply-To: <000000000000f020a905f061d4c2@google.com>
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
On 12/21, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 77856d911a8c Merge tag 'arm64-fixes' of git://git.kernel.o..
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=17c418c8480000
> kernel config: https://syzkaller.appspot.com/x/.config?x=f967143badd2fa39
> dashboard link: https://syzkaller.appspot.com/bug?extid=e1246909d526a9d470fa
> compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=160ea04f880000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e2a99d880000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/4b424d9203f5/disk-77856d91.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/47fd68051834/vmlinux-77856d91.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/d3091f087a86/bzImage-77856d91.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/36b1377afaef/mount_0.gz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+e1246909d526a9d470fa@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/inode.c:864!
> invalid opcode: 0000 [#1] PREEMPT SMP KASAN
> CPU: 1 PID: 5067 Comm: syz-executor118 Not tainted 6.1.0-syzkaller-13031-g77856d911a8c #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
> RIP: 0010:f2fs_evict_inode+0x1306/0x1310 fs/f2fs/inode.c:864
> Code: ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 8a f5 ff ff 48 89 df e8 4b 51 1a fe e9 7d f5 ff ff e8 e1 b4 c4 fd 0f 0b e8 da b4 c4 fd <0f> 0b 0f 1f 84 00 00 00 00 00 55 41 57 41 56 53 48 89 fb e8 c2 b4
> RSP: 0018:ffffc90003b3f8f8 EFLAGS: 00010293
> RAX: ffffffff83c720e6 RBX: 0000000000000002 RCX: ffff8880251257c0
> RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
> RBP: 0000000000000000 R08: ffffffff83c71bc3 R09: ffffed100e5a41b5
> R10: ffffed100e5a41b5 R11: 1ffff1100e5a41b4 R12: dffffc0000000000
> R13: ffff888072d208f0 R14: ffff888072d20da0 R15: 0000000000000000
> FS: 000055555685a300(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007ffd85832d68 CR3: 00000000726a5000 CR4: 00000000003506e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> <TASK>
> evict+0x2a4/0x620 fs/inode.c:664
> dispose_list fs/inode.c:697 [inline]
> evict_inodes+0x658/0x700 fs/inode.c:747
> generic_shutdown_super+0x94/0x310 fs/super.c:480
> kill_block_super+0x79/0xd0 fs/super.c:1386
> kill_f2fs_super+0x2f9/0x3c0 fs/f2fs/super.c:4640
> deactivate_locked_super+0xa7/0xf0 fs/super.c:332
> cleanup_mnt+0x494/0x520 fs/namespace.c:1291
> task_work_run+0x243/0x300 kernel/task_work.c:179
> ptrace_notify+0x29a/0x340 kernel/signal.c:2354
> ptrace_report_syscall include/linux/ptrace.h:411 [inline]
> ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]
> syscall_exit_work+0x8c/0xe0 kernel/entry/common.c:251
> syscall_exit_to_user_mode_prepare+0x63/0xc0 kernel/entry/common.c:278
> __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
> syscall_exit_to_user_mode+0xa/0x60 kernel/entry/common.c:296
> do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
> entry_SYSCALL_64_after_hwframe+0x63/0xcd
> RIP: 0033:0x7fd8e1d06d97
> Code: 08 00 48 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007ffd858334a8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a6
> RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007fd8e1d06d97
> RDX: 00007ffd85833569 RSI: 000000000000000a RDI: 00007ffd85833560
> RBP: 00007ffd85833560 R08: 00000000ffffffff R09: 00007ffd85833340
> R10: 000055555685b653 R11: 0000000000000202 R12: 00007ffd858345d0
> R13: 000055555685b5f0 R14: 00007ffd858334d0 R15: 0000000000000001
> </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:f2fs_evict_inode+0x1306/0x1310 fs/f2fs/inode.c:864
> Code: ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 8a f5 ff ff 48 89 df e8 4b 51 1a fe e9 7d f5 ff ff e8 e1 b4 c4 fd 0f 0b e8 da b4 c4 fd <0f> 0b 0f 1f 84 00 00 00 00 00 55 41 57 41 56 53 48 89 fb e8 c2 b4
> RSP: 0018:ffffc90003b3f8f8 EFLAGS: 00010293
> RAX: ffffffff83c720e6 RBX: 0000000000000002 RCX: ffff8880251257c0
> RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
> RBP: 0000000000000000 R08: ffffffff83c71bc3 R09: ffffed100e5a41b5
> R10: ffffed100e5a41b5 R11: 1ffff1100e5a41b4 R12: dffffc0000000000
> R13: ffff888072d208f0 R14: ffff888072d20da0 R15: 0000000000000000
> FS: 000055555685a300(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007ffd85832d68 CR3: 00000000726a5000 CR4: 00000000003506e0
> 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 syzkaller@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
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: syzbot <syzbot+e1246909d526a9d470fa@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, chao@kernel.org, hughd@google.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] [tmpfs?] kernel BUG in f2fs_evict_inode
Date: Fri, 7 Jul 2023 07:20:11 -0700 [thread overview]
Message-ID: <ZKgfG5yE+VoMiVsZ@google.com> (raw)
In-Reply-To: <000000000000f020a905f061d4c2@google.com>
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
On 12/21, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 77856d911a8c Merge tag 'arm64-fixes' of git://git.kernel.o..
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=17c418c8480000
> kernel config: https://syzkaller.appspot.com/x/.config?x=f967143badd2fa39
> dashboard link: https://syzkaller.appspot.com/bug?extid=e1246909d526a9d470fa
> compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=160ea04f880000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e2a99d880000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/4b424d9203f5/disk-77856d91.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/47fd68051834/vmlinux-77856d91.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/d3091f087a86/bzImage-77856d91.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/36b1377afaef/mount_0.gz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+e1246909d526a9d470fa@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/inode.c:864!
> invalid opcode: 0000 [#1] PREEMPT SMP KASAN
> CPU: 1 PID: 5067 Comm: syz-executor118 Not tainted 6.1.0-syzkaller-13031-g77856d911a8c #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
> RIP: 0010:f2fs_evict_inode+0x1306/0x1310 fs/f2fs/inode.c:864
> Code: ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 8a f5 ff ff 48 89 df e8 4b 51 1a fe e9 7d f5 ff ff e8 e1 b4 c4 fd 0f 0b e8 da b4 c4 fd <0f> 0b 0f 1f 84 00 00 00 00 00 55 41 57 41 56 53 48 89 fb e8 c2 b4
> RSP: 0018:ffffc90003b3f8f8 EFLAGS: 00010293
> RAX: ffffffff83c720e6 RBX: 0000000000000002 RCX: ffff8880251257c0
> RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
> RBP: 0000000000000000 R08: ffffffff83c71bc3 R09: ffffed100e5a41b5
> R10: ffffed100e5a41b5 R11: 1ffff1100e5a41b4 R12: dffffc0000000000
> R13: ffff888072d208f0 R14: ffff888072d20da0 R15: 0000000000000000
> FS: 000055555685a300(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007ffd85832d68 CR3: 00000000726a5000 CR4: 00000000003506e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> <TASK>
> evict+0x2a4/0x620 fs/inode.c:664
> dispose_list fs/inode.c:697 [inline]
> evict_inodes+0x658/0x700 fs/inode.c:747
> generic_shutdown_super+0x94/0x310 fs/super.c:480
> kill_block_super+0x79/0xd0 fs/super.c:1386
> kill_f2fs_super+0x2f9/0x3c0 fs/f2fs/super.c:4640
> deactivate_locked_super+0xa7/0xf0 fs/super.c:332
> cleanup_mnt+0x494/0x520 fs/namespace.c:1291
> task_work_run+0x243/0x300 kernel/task_work.c:179
> ptrace_notify+0x29a/0x340 kernel/signal.c:2354
> ptrace_report_syscall include/linux/ptrace.h:411 [inline]
> ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]
> syscall_exit_work+0x8c/0xe0 kernel/entry/common.c:251
> syscall_exit_to_user_mode_prepare+0x63/0xc0 kernel/entry/common.c:278
> __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
> syscall_exit_to_user_mode+0xa/0x60 kernel/entry/common.c:296
> do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
> entry_SYSCALL_64_after_hwframe+0x63/0xcd
> RIP: 0033:0x7fd8e1d06d97
> Code: 08 00 48 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007ffd858334a8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a6
> RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007fd8e1d06d97
> RDX: 00007ffd85833569 RSI: 000000000000000a RDI: 00007ffd85833560
> RBP: 00007ffd85833560 R08: 00000000ffffffff R09: 00007ffd85833340
> R10: 000055555685b653 R11: 0000000000000202 R12: 00007ffd858345d0
> R13: 000055555685b5f0 R14: 00007ffd858334d0 R15: 0000000000000001
> </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:f2fs_evict_inode+0x1306/0x1310 fs/f2fs/inode.c:864
> Code: ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 8a f5 ff ff 48 89 df e8 4b 51 1a fe e9 7d f5 ff ff e8 e1 b4 c4 fd 0f 0b e8 da b4 c4 fd <0f> 0b 0f 1f 84 00 00 00 00 00 55 41 57 41 56 53 48 89 fb e8 c2 b4
> RSP: 0018:ffffc90003b3f8f8 EFLAGS: 00010293
> RAX: ffffffff83c720e6 RBX: 0000000000000002 RCX: ffff8880251257c0
> RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
> RBP: 0000000000000000 R08: ffffffff83c71bc3 R09: ffffed100e5a41b5
> R10: ffffed100e5a41b5 R11: 1ffff1100e5a41b4 R12: dffffc0000000000
> R13: ffff888072d208f0 R14: ffff888072d20da0 R15: 0000000000000000
> FS: 000055555685a300(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007ffd85832d68 CR3: 00000000726a5000 CR4: 00000000003506e0
> 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 syzkaller@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
next prev parent reply other threads:[~2023-07-07 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 2:57 [f2fs-dev] [syzbot] [f2fs?] [tmpfs?] kernel BUG in f2fs_evict_inode syzbot
2022-12-22 2:57 ` syzbot
2023-07-07 14:20 ` Jaegeuk Kim [this message]
2023-07-07 14:20 ` Jaegeuk Kim
2023-07-07 14:45 ` [f2fs-dev] [syzbot] [f2fs?] " syzbot
2023-07-07 14:45 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZKgfG5yE+VoMiVsZ@google.com \
--to=jaegeuk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+e1246909d526a9d470fa@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.