From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: print message if fscorrupted was found in f2fs_new_node_page()
Date: Sat, 23 Nov 2024 15:50:38 +0000 [thread overview]
Message-ID: <173237703828.3018181.12274971002493220671.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241120065850.1345670-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 20 Nov 2024 14:58:50 +0800 you wrote:
> If fs corruption occurs in f2fs_new_node_page(), let's print
> more information about corrupted metadata into kernel log.
>
> Meanwhile, it updates to record ERROR_INCONSISTENT_NAT instead
> of ERROR_INVALID_BLKADDR if blkaddr in nat entry is not
> NULL_ADDR which means nat bitmap and nat entry is inconsistent.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: print message if fscorrupted was found in f2fs_new_node_page()
https://git.kernel.org/jaegeuk/f2fs/c/81520c684ca6
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-11-23 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 6:58 [PATCH] f2fs: print message if fscorrupted was found in f2fs_new_node_page() Chao Yu
2024-11-23 15:50 ` 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=173237703828.3018181.12274971002493220671.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 \
/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