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 1/3] f2fs: do sanity check on inode footer in f2fs_get_inode_page()
Date: Tue, 04 Mar 2025 17:10:48 +0000 [thread overview]
Message-ID: <174110824849.224349.8255576653519442579.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250303035423.1357211-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 3 Mar 2025 11:54:21 +0800 you wrote:
> This patch introduces a new wrapper f2fs_get_inode_page(), then, caller
> can use it to load inode block to page cache, meanwhile it will do sanity
> check on inode footer.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> fs/f2fs/data.c | 6 ++---
> fs/f2fs/dir.c | 2 +-
> fs/f2fs/f2fs.h | 3 ++-
> fs/f2fs/file.c | 2 +-
> fs/f2fs/inline.c | 22 +++++++++----------
> fs/f2fs/inode.c | 4 ++--
> fs/f2fs/node.c | 57 +++++++++++++++++++++++++++++++++---------------
> fs/f2fs/node.h | 6 +++++
> fs/f2fs/xattr.c | 4 ++--
> 9 files changed, 67 insertions(+), 39 deletions(-)
Here is the summary with links:
- [f2fs-dev,1/3] f2fs: do sanity check on inode footer in f2fs_get_inode_page()
https://git.kernel.org/jaegeuk/f2fs/c/770648dd6abc
- [f2fs-dev,2/3] f2fs: do sanity check on xattr node footer in f2fs_get_xnode_page()
https://git.kernel.org/jaegeuk/f2fs/c/1078ec609e0a
- [f2fs-dev,3/3] f2fs: introduce FAULT_INCONSISTENT_FOOTER
https://git.kernel.org/jaegeuk/f2fs/c/4116a6f1172c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-03-04 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 3:54 [PATCH 1/3] f2fs: do sanity check on inode footer in f2fs_get_inode_page() Chao Yu
2025-03-03 3:54 ` [PATCH 2/3] f2fs: do sanity check on xattr node footer in f2fs_get_xnode_page() Chao Yu
2025-03-03 3:54 ` [PATCH 3/3] f2fs: introduce FAULT_INCONSISTENT_FOOTER Chao Yu
2025-03-04 17:10 ` patchwork-bot+f2fs [this message]
2025-03-05 6:39 ` [f2fs-dev] [PATCH 1/3] f2fs: do sanity check on inode footer in f2fs_get_inode_page() Zhiguo Niu
2025-03-05 8:27 ` Chao Yu
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=174110824849.224349.8255576653519442579.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