From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
daehojeong@google.com, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH 1/4] f2fs: atomic: fix to avoid racing w/ GC
Date: Mon, 05 Aug 2024 23:30:51 +0000 [thread overview]
Message-ID: <172290065184.2803.16077457643424916047.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240625031351.3586955-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 25 Jun 2024 11:13:48 +0800 you wrote:
> Case #1:
> SQLite App GC Thread Kworker Shrinker
> - f2fs_ioc_start_atomic_write
>
> - f2fs_ioc_commit_atomic_write
> - f2fs_commit_atomic_write
> - filemap_write_and_wait_range
> : write atomic_file's data to cow_inode
> echo 3 > drop_caches
> to drop atomic_file's
> cache.
> - f2fs_gc
> - gc_data_segment
> - move_data_page
> - set_page_dirty
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/4] f2fs: atomic: fix to avoid racing w/ GC
https://git.kernel.org/jaegeuk/f2fs/c/1a0bd289a5db
- [f2fs-dev,2/4] f2fs: atomic: fix to not allow GC to pollute atomic_file
https://git.kernel.org/jaegeuk/f2fs/c/7566a155c666
- [f2fs-dev,3/4] f2fs: atomic: fix to truncate pagecache before on-disk metadata truncation
(no matching commit)
- [f2fs-dev,4/4] f2fs: atomic: fix to forbid dio in atomic_file
https://git.kernel.org/jaegeuk/f2fs/c/374a8881ce4c
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:[~2024-08-05 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 3:13 [f2fs-dev] [PATCH 1/4] f2fs: atomic: fix to avoid racing w/ GC Chao Yu
2024-06-25 3:13 ` [f2fs-dev] [PATCH 2/4] f2fs: atomic: fix to not allow GC to pollute atomic_file Chao Yu
2024-06-25 3:13 ` [f2fs-dev] [PATCH 3/4] f2fs: atomic: fix to truncate pagecache before on-disk metadata truncation Chao Yu
2024-07-25 20:54 ` Jaegeuk Kim
2024-07-26 1:06 ` Chao Yu
2024-06-25 3:13 ` [f2fs-dev] [PATCH 4/4] f2fs: atomic: fix to forbid dio in atomic_file Chao Yu
2024-07-02 12:13 ` Sunmin Jeong
2024-08-05 23:30 ` 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=172290065184.2803.16077457643424916047.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;
as well as URLs for NNTP newsgroup(s).