From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, daehojeong@google.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v5 1/6] f2fs: compress: fix to guarantee persisting compressed blocks by CP
Date: Mon, 29 Jan 2024 20:29:30 +0000 [thread overview]
Message-ID: <170656017092.16041.5056529810169892695.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240112194132.25637-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sat, 13 Jan 2024 03:41:27 +0800 you wrote:
> If data block in compressed cluster is not persisted with metadata
> during checkpoint, after SPOR, the data may be corrupted, let's
> guarantee to write compressed page by checkpoint.
>
> Fixes: 4c8ff7095bef ("f2fs: support data compression")
> Reviewed-by: Daeho Jeong <daehojeong@google.com>
> Signed-off-by: Chao Yu <chao@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,v5,1/6] f2fs: compress: fix to guarantee persisting compressed blocks by CP
https://git.kernel.org/jaegeuk/f2fs/c/fe2b98bcae7e
- [f2fs-dev,v5,2/6] f2fs: compress: fix to cover normal cluster write with cp_rwsem
https://git.kernel.org/jaegeuk/f2fs/c/bd0dddafd4a5
- [f2fs-dev,v5,3/6] f2fs: compress: fix to check unreleased compressed cluster
https://git.kernel.org/jaegeuk/f2fs/c/787f217e7f04
- [f2fs-dev,v5,4/6] f2fs: compress: fix to avoid inconsistence bewteen i_blocks and dnode
https://git.kernel.org/jaegeuk/f2fs/c/6d05c8d5997a
- [f2fs-dev,v5,5/6] f2fs: fix to remove unnecessary f2fs_bug_on() to avoid panic
https://git.kernel.org/jaegeuk/f2fs/c/ef62f2496f99
- [f2fs-dev,v5,6/6] f2fs: introduce FAULT_BLKADDR_CONSISTENCE
https://git.kernel.org/jaegeuk/f2fs/c/e2c2cb1a331f
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-01-29 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 19:41 [PATCH v5 1/6] f2fs: compress: fix to guarantee persisting compressed blocks by CP Chao Yu
2024-01-12 19:41 ` [PATCH v5 2/6] f2fs: compress: fix to cover normal cluster write with cp_rwsem Chao Yu
2024-01-12 19:41 ` [PATCH v5 3/6] f2fs: compress: fix to check unreleased compressed cluster Chao Yu
2024-01-12 19:41 ` [PATCH v5 4/6] f2fs: compress: fix to avoid inconsistence bewteen i_blocks and dnode Chao Yu
2024-01-12 19:41 ` [PATCH v5 5/6] f2fs: fix to remove unnecessary f2fs_bug_on() to avoid panic Chao Yu
2024-01-12 19:41 ` [PATCH v5 6/6] f2fs: introduce FAULT_BLKADDR_CONSISTENCE Chao Yu
2024-01-29 20:29 ` 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=170656017092.16041.5056529810169892695.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=daehojeong@google.com \
--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