From: Chao Yu <chao@kernel.org>
To: syzbot <syzbot+31e4659a3fe953aec2f4@syzkaller.appspotmail.com>,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] kernel BUG in f2fs_evict_inode (2)
Date: Tue, 4 Jun 2024 22:44:53 +0800 [thread overview]
Message-ID: <a67e82fc-4658-4784-8d5b-e8a048e749e2@kernel.org> (raw)
In-Reply-To: <000000000000e890bc0609a55cff@google.com>
#syz test: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git wip
On 2023/11/8 23:01, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 90b0c2b2edd1 Merge tag 'pinctrl-v6.7-1' of git://git.kerne..
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=10222eeb680000
> kernel config: https://syzkaller.appspot.com/x/.config?x=93ac5233c138249e
> dashboard link: https://syzkaller.appspot.com/bug?extid=31e4659a3fe953aec2f4
> 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=13a2847b680000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1579d0df680000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/10c213d23300/disk-90b0c2b2.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/0c55e6e441c1/vmlinux-90b0c2b2.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/c7f0436ea052/bzImage-90b0c2b2.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/dbf260983b94/mount_0.gz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+31e4659a3fe953aec2f4@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/inode.c:933!
> invalid opcode: 0000 [#1] PREEMPT SMP KASAN
> CPU: 1 PID: 5054 Comm: syz-executor410 Not tainted 6.6.0-syzkaller-14142-g90b0c2b2edd1 #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
> RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933
> Code: fd 31 ff 89 de e8 5a 4f bf fd 40 84 ed 75 29 e8 c0 4c bf fd 4c 8b 74 24 08 e9 c9 eb ff ff e8 b1 4c bf fd 0f 0b e8 aa 4c bf fd <0f> 0b e8 a3 4c bf fd 0f 0b e9 f6 fe ff ff e8 97 4c bf fd e8 72 e7
> RSP: 0018:ffffc900039df918 EFLAGS: 00010293
> RAX: ffffffff83cf9f56 RBX: 0000000000000002 RCX: ffff888014b30000
> RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
> RBP: 0000000000000000 R08: ffffffff83cf984a R09: 1ffff1100ed0061d
> R10: dffffc0000000000 R11: ffffed100ed0061e R12: 1ffff1100ed0058f
> R13: ffff888076802c38 R14: ffff8880768030e8 R15: dffffc0000000000
> FS: 00005555556ae3c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007ffdbe23ce18 CR3: 00000000727e8000 CR4: 00000000003506f0
> 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+0x5f8/0x690 fs/inode.c:747
> generic_shutdown_super+0x9d/0x2c0 fs/super.c:675
> kill_block_super+0x44/0x90 fs/super.c:1667
> kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894
> deactivate_locked_super+0xc1/0x130 fs/super.c:484
> cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256
> task_work_run+0x24a/0x300 kernel/task_work.c:180
> ptrace_notify+0x2cd/0x380 kernel/signal.c:2399
> ptrace_report_syscall include/linux/ptrace.h:411 [inline]
> ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]
> syscall_exit_work kernel/entry/common.c:251 [inline]
> syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline]
> __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
> syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296
> do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88
> entry_SYSCALL_64_after_hwframe+0x63/0x6b
> RIP: 0033:0x7fa1a5e8ee77
> 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 00 f0 ff ff 77 01 c3 48 c7 c2 b0 ff ff ff f7 d8 64 89 02 b8
> RSP: 002b:00007ffdbe23d5c8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a6
> RAX: 0000000000000000 RBX: 0000000000021a97 RCX: 00007fa1a5e8ee77
> RDX: 0000000000000000 RSI: 000000000000000a RDI: 00007ffdbe23d680
> RBP: 00007ffdbe23d680 R08: 0000000000000000 R09: 0000000000000000
> R10: 00000000ffffffff R11: 0000000000000202 R12: 00007ffdbe23e740
> R13: 00005555556af700 R14: 431bde82d7b634db R15: 00007ffdbe23e6e4
> </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933
> Code: fd 31 ff 89 de e8 5a 4f bf fd 40 84 ed 75 29 e8 c0 4c bf fd 4c 8b 74 24 08 e9 c9 eb ff ff e8 b1 4c bf fd 0f 0b e8 aa 4c bf fd <0f> 0b e8 a3 4c bf fd 0f 0b e9 f6 fe ff ff e8 97 4c bf fd e8 72 e7
> RSP: 0018:ffffc900039df918 EFLAGS: 00010293
> RAX: ffffffff83cf9f56 RBX: 0000000000000002 RCX: ffff888014b30000
> RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
> RBP: 0000000000000000 R08: ffffffff83cf984a R09: 1ffff1100ed0061d
> R10: dffffc0000000000 R11: ffffed100ed0061e R12: 1ffff1100ed0058f
> R13: ffff888076802c38 R14: ffff8880768030e8 R15: dffffc0000000000
> FS: 00005555556ae3c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007ffdbe23ce18 CR3: 00000000727e8000 CR4: 00000000003506f0
> 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.
>
> If the report is already addressed, 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 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
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: syzbot <syzbot+31e4659a3fe953aec2f4@syzkaller.appspotmail.com>,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] kernel BUG in f2fs_evict_inode (2)
Date: Tue, 4 Jun 2024 22:44:53 +0800 [thread overview]
Message-ID: <a67e82fc-4658-4784-8d5b-e8a048e749e2@kernel.org> (raw)
In-Reply-To: <000000000000e890bc0609a55cff@google.com>
#syz test: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git wip
On 2023/11/8 23:01, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 90b0c2b2edd1 Merge tag 'pinctrl-v6.7-1' of git://git.kerne..
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=10222eeb680000
> kernel config: https://syzkaller.appspot.com/x/.config?x=93ac5233c138249e
> dashboard link: https://syzkaller.appspot.com/bug?extid=31e4659a3fe953aec2f4
> 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=13a2847b680000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1579d0df680000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/10c213d23300/disk-90b0c2b2.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/0c55e6e441c1/vmlinux-90b0c2b2.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/c7f0436ea052/bzImage-90b0c2b2.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/dbf260983b94/mount_0.gz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+31e4659a3fe953aec2f4@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/inode.c:933!
> invalid opcode: 0000 [#1] PREEMPT SMP KASAN
> CPU: 1 PID: 5054 Comm: syz-executor410 Not tainted 6.6.0-syzkaller-14142-g90b0c2b2edd1 #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
> RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933
> Code: fd 31 ff 89 de e8 5a 4f bf fd 40 84 ed 75 29 e8 c0 4c bf fd 4c 8b 74 24 08 e9 c9 eb ff ff e8 b1 4c bf fd 0f 0b e8 aa 4c bf fd <0f> 0b e8 a3 4c bf fd 0f 0b e9 f6 fe ff ff e8 97 4c bf fd e8 72 e7
> RSP: 0018:ffffc900039df918 EFLAGS: 00010293
> RAX: ffffffff83cf9f56 RBX: 0000000000000002 RCX: ffff888014b30000
> RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
> RBP: 0000000000000000 R08: ffffffff83cf984a R09: 1ffff1100ed0061d
> R10: dffffc0000000000 R11: ffffed100ed0061e R12: 1ffff1100ed0058f
> R13: ffff888076802c38 R14: ffff8880768030e8 R15: dffffc0000000000
> FS: 00005555556ae3c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007ffdbe23ce18 CR3: 00000000727e8000 CR4: 00000000003506f0
> 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+0x5f8/0x690 fs/inode.c:747
> generic_shutdown_super+0x9d/0x2c0 fs/super.c:675
> kill_block_super+0x44/0x90 fs/super.c:1667
> kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894
> deactivate_locked_super+0xc1/0x130 fs/super.c:484
> cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256
> task_work_run+0x24a/0x300 kernel/task_work.c:180
> ptrace_notify+0x2cd/0x380 kernel/signal.c:2399
> ptrace_report_syscall include/linux/ptrace.h:411 [inline]
> ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]
> syscall_exit_work kernel/entry/common.c:251 [inline]
> syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline]
> __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
> syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296
> do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88
> entry_SYSCALL_64_after_hwframe+0x63/0x6b
> RIP: 0033:0x7fa1a5e8ee77
> 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 00 f0 ff ff 77 01 c3 48 c7 c2 b0 ff ff ff f7 d8 64 89 02 b8
> RSP: 002b:00007ffdbe23d5c8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a6
> RAX: 0000000000000000 RBX: 0000000000021a97 RCX: 00007fa1a5e8ee77
> RDX: 0000000000000000 RSI: 000000000000000a RDI: 00007ffdbe23d680
> RBP: 00007ffdbe23d680 R08: 0000000000000000 R09: 0000000000000000
> R10: 00000000ffffffff R11: 0000000000000202 R12: 00007ffdbe23e740
> R13: 00005555556af700 R14: 431bde82d7b634db R15: 00007ffdbe23e6e4
> </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933
> Code: fd 31 ff 89 de e8 5a 4f bf fd 40 84 ed 75 29 e8 c0 4c bf fd 4c 8b 74 24 08 e9 c9 eb ff ff e8 b1 4c bf fd 0f 0b e8 aa 4c bf fd <0f> 0b e8 a3 4c bf fd 0f 0b e9 f6 fe ff ff e8 97 4c bf fd e8 72 e7
> RSP: 0018:ffffc900039df918 EFLAGS: 00010293
> RAX: ffffffff83cf9f56 RBX: 0000000000000002 RCX: ffff888014b30000
> RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
> RBP: 0000000000000000 R08: ffffffff83cf984a R09: 1ffff1100ed0061d
> R10: dffffc0000000000 R11: ffffed100ed0061e R12: 1ffff1100ed0058f
> R13: ffff888076802c38 R14: ffff8880768030e8 R15: dffffc0000000000
> FS: 00005555556ae3c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007ffdbe23ce18 CR3: 00000000727e8000 CR4: 00000000003506f0
> 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.
>
> If the report is already addressed, 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 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
next prev parent reply other threads:[~2024-06-04 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 15:01 [f2fs-dev] [syzbot] [f2fs?] kernel BUG in f2fs_evict_inode (2) syzbot
2023-11-08 15:01 ` syzbot
2024-06-04 14:44 ` Chao Yu [this message]
2024-06-04 14:44 ` Chao Yu
2024-06-04 15:10 ` [f2fs-dev] " syzbot
2024-06-04 15:10 ` 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=a67e82fc-4658-4784-8d5b-e8a048e749e2@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+31e4659a3fe953aec2f4@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.