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 v2] f2fs: fix to truncate meta inode pages forcely
Date: Wed, 13 Mar 2024 01:30:29 +0000 [thread overview]
Message-ID: <171029342991.17296.1644689290423723789.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240308010834.4023772-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 8 Mar 2024 09:08:34 +0800 you wrote:
> Below race case can cause data corruption:
>
> Thread A GC thread
> - gc_data_segment
> - ra_data_block
> - locked meta_inode page
> - f2fs_inplace_write_data
> - invalidate_mapping_pages
> : fail to invalidate meta_inode page
> due to lock failure or dirty|writeback
> status
> - f2fs_submit_page_bio
> : write last dirty data to old blkaddr
> - move_data_block
> - load old data from meta_inode page
> - f2fs_submit_page_write
> : write old data to new blkaddr
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix to truncate meta inode pages forcely
https://git.kernel.org/jaegeuk/f2fs/c/9f0c4a46be1f
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-03-13 1:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 1:08 [PATCH v2] f2fs: fix to truncate meta inode pages forcely Chao Yu
2024-03-13 1: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=171029342991.17296.1644689290423723789.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