From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org,
syzbot+ebea2790904673d7c618@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: get rid of online repaire on corrupted directory
Date: Mon, 16 Sep 2024 21:30:38 +0000 [thread overview]
Message-ID: <172652223875.3820990.5151598286635393871.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240906062724.3569496-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 6 Sep 2024 14:27:24 +0800 you wrote:
> syzbot reports a f2fs bug as below:
>
> kernel BUG at fs/f2fs/inode.c:896!
> RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896
> Call Trace:
> evict+0x532/0x950 fs/inode.c:704
> dispose_list fs/inode.c:747 [inline]
> evict_inodes+0x5f9/0x690 fs/inode.c:797
> generic_shutdown_super+0x9d/0x2d0 fs/super.c:627
> kill_block_super+0x44/0x90 fs/super.c:1696
> kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898
> 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:228
> ptrace_notify+0x2d2/0x380 kernel/signal.c:2402
> ptrace_report_syscall include/linux/ptrace.h:415 [inline]
> ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline]
> syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173
> syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline]
> __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline]
> syscall_exit_to_user_mode+0x279/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: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: get rid of online repaire on corrupted directory
https://git.kernel.org/jaegeuk/f2fs/c/884ee6dc85b9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-09-16 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 6:27 [PATCH] f2fs: get rid of online repaire on corrupted directory Chao Yu
2024-09-16 21:30 ` patchwork-bot+f2fs [this message]
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=172652223875.3820990.5151598286635393871.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+ebea2790904673d7c618@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox