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] f2fs: fix to wait on page writeback in __clone_blkaddrs()
Date: Sun, 14 Apr 2024 15:32:45 +0000 [thread overview]
Message-ID: <171310876507.3156.2662208686749241669.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240326112845.1576111-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 26 Mar 2024 19:28:45 +0800 you wrote:
> In below race condition, dst page may become writeback status
> in __clone_blkaddrs(), it needs to wait writeback before update,
> fix it.
>
> Thread A GC Thread
> - f2fs_move_file_range
> - filemap_write_and_wait_range(dst)
> - gc_data_segment
> - f2fs_down_write(dst)
> - move_data_page
> - set_page_writeback(dst_page)
> - f2fs_submit_page_write
> - f2fs_up_write(dst)
> - f2fs_down_write(dst)
> - __exchange_data_block
> - __clone_blkaddrs
> - f2fs_get_new_data_page
> - memcpy_page
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to wait on page writeback in __clone_blkaddrs()
https://git.kernel.org/jaegeuk/f2fs/c/d3876e34e7e7
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-04-14 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 11:28 [f2fs-dev] [PATCH] f2fs: fix to wait on page writeback in __clone_blkaddrs() Chao Yu
2024-04-14 15:32 ` 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=171310876507.3156.2662208686749241669.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).