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/6] f2fs: fix to tag gcing flag on page during block migration
Date: Thu, 14 Dec 2023 20:50:31 +0000 [thread overview]
Message-ID: <170258703195.30587.3513758411413071845.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231210113547.3412782-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sun, 10 Dec 2023 19:35:42 +0800 you wrote:
> It needs to add missing gcing flag on page during block migration,
> in order to garantee migrated data be persisted during checkpoint,
> otherwise out-of-order persistency between data and node may cause
> data corruption after SPOR.
>
> Similar issue was fixed by commit 2d1fe8a86bf5 ("f2fs: fix to tag
> gcing flag on page during file defragment").
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/6] f2fs: fix to tag gcing flag on page during block migration
https://git.kernel.org/jaegeuk/f2fs/c/4961acdd65c9
- [f2fs-dev,2/6] f2fs: fix to wait on block writeback for post_read case
https://git.kernel.org/jaegeuk/f2fs/c/55fdc1c24a1d
- [f2fs-dev,3/6] f2fs: fix to check compress file in f2fs_move_file_range()
https://git.kernel.org/jaegeuk/f2fs/c/fb9b65340c81
- [f2fs-dev,4/6] f2fs: don't set FI_PREALLOCATED_ALL for partial write
(no matching commit)
- [f2fs-dev,5/6] f2fs: fix to restrict condition of compress inode conversion
(no matching commit)
- [f2fs-dev,6/6] f2fs: fix to update iostat correctly in f2fs_filemap_fault()
https://git.kernel.org/jaegeuk/f2fs/c/bb34cc6ca87f
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
WARNING: multiple messages have this Message-ID (diff)
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/6] f2fs: fix to tag gcing flag on page during block migration
Date: Thu, 14 Dec 2023 20:50:31 +0000 [thread overview]
Message-ID: <170258703195.30587.3513758411413071845.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231210113547.3412782-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sun, 10 Dec 2023 19:35:42 +0800 you wrote:
> It needs to add missing gcing flag on page during block migration,
> in order to garantee migrated data be persisted during checkpoint,
> otherwise out-of-order persistency between data and node may cause
> data corruption after SPOR.
>
> Similar issue was fixed by commit 2d1fe8a86bf5 ("f2fs: fix to tag
> gcing flag on page during file defragment").
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/6] f2fs: fix to tag gcing flag on page during block migration
https://git.kernel.org/jaegeuk/f2fs/c/4961acdd65c9
- [f2fs-dev,2/6] f2fs: fix to wait on block writeback for post_read case
https://git.kernel.org/jaegeuk/f2fs/c/55fdc1c24a1d
- [f2fs-dev,3/6] f2fs: fix to check compress file in f2fs_move_file_range()
https://git.kernel.org/jaegeuk/f2fs/c/fb9b65340c81
- [f2fs-dev,4/6] f2fs: don't set FI_PREALLOCATED_ALL for partial write
(no matching commit)
- [f2fs-dev,5/6] f2fs: fix to restrict condition of compress inode conversion
(no matching commit)
- [f2fs-dev,6/6] f2fs: fix to update iostat correctly in f2fs_filemap_fault()
https://git.kernel.org/jaegeuk/f2fs/c/bb34cc6ca87f
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:[~2023-12-14 20:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 11:35 [f2fs-dev] [PATCH 1/6] f2fs: fix to tag gcing flag on page during block migration Chao Yu
2023-12-10 11:35 ` Chao Yu
2023-12-10 11:35 ` [f2fs-dev] [PATCH 2/6] f2fs: fix to wait on block writeback for post_read case Chao Yu
2023-12-10 11:35 ` Chao Yu
2023-12-10 11:35 ` [f2fs-dev] [PATCH 3/6] f2fs: fix to check compress file in f2fs_move_file_range() Chao Yu
2023-12-10 11:35 ` Chao Yu
2023-12-10 11:35 ` [f2fs-dev] [PATCH 4/6] f2fs: don't set FI_PREALLOCATED_ALL for partial write Chao Yu
2023-12-10 11:35 ` Chao Yu
2023-12-11 22:08 ` [f2fs-dev] " Jaegeuk Kim
2023-12-11 22:08 ` Jaegeuk Kim
2023-12-10 11:35 ` [f2fs-dev] [PATCH 5/6] f2fs: fix to restrict condition of compress inode conversion Chao Yu
2023-12-10 11:35 ` Chao Yu
2023-12-11 22:11 ` [f2fs-dev] " Jaegeuk Kim
2023-12-11 22:11 ` Jaegeuk Kim
2023-12-12 1:05 ` [f2fs-dev] " Chao Yu
2023-12-12 1:05 ` Chao Yu
2023-12-12 22:21 ` [f2fs-dev] " Jaegeuk Kim
2023-12-12 22:21 ` Jaegeuk Kim
2023-12-28 15:33 ` [f2fs-dev] " Chao Yu
2023-12-28 15:33 ` Chao Yu
2024-01-02 22:54 ` [f2fs-dev] " Jaegeuk Kim
2024-01-02 22:54 ` Jaegeuk Kim
2024-01-11 3:07 ` [f2fs-dev] " Chao Yu
2024-01-11 3:07 ` Chao Yu
2023-12-10 11:35 ` [f2fs-dev] [PATCH 6/6] f2fs: fix to update iostat correctly in f2fs_filemap_fault() Chao Yu
2023-12-10 11:35 ` Chao Yu
2023-12-14 20:50 ` patchwork-bot+f2fs [this message]
2023-12-14 20:50 ` [f2fs-dev] [PATCH 1/6] f2fs: fix to tag gcing flag on page during block migration patchwork-bot+f2fs
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=170258703195.30587.3513758411413071845.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.