From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: fix to do sanity check on node folio during its writeback
Date: Tue, 11 Nov 2025 22:50:16 +0000 [thread overview]
Message-ID: <176290141623.3596344.10698680340121924794.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251011123016.715964-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sat, 11 Oct 2025 20:30:15 +0800 you wrote:
> Add more sanity check on node folio during its writeback, if node footer
> indicates it is an inode:
> - i_mode should be consistent w/ inode
> - ofs_of_node should be consistent w/ non-xattr node
>
> In addition, if sanity check fails, let's shutdown filesystem to avoid
> looping to redirty and writeback it.
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: fix to do sanity check on node folio during its writeback
https://git.kernel.org/jaegeuk/f2fs/c/b63e02895b26
- [f2fs-dev,2/2] f2fs: fix to do sanity check on node footer in {read, write}_end_io
https://git.kernel.org/jaegeuk/f2fs/c/3bae3cbbf1a8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2025-11-11 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 12:30 [f2fs-dev] [PATCH 1/2] f2fs: fix to do sanity check on node folio during its writeback Chao Yu via Linux-f2fs-devel
2025-10-11 12:30 ` [f2fs-dev] [PATCH 2/2] f2fs: fix to do sanity check on node footer in {read, write}_end_io Chao Yu via Linux-f2fs-devel
2025-11-11 22:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=176290141623.3596344.10698680340121924794.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).