Received-SPF: pass (google.com: domain of linux-kernel+bounces-101018-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix to truncate meta inode pages forcely
From: patchwork-bot+f2fs@kernel.org
Message-Id: 
 <171029342991.17296.1644689290423723789.git-patchwork-notify@kernel.org>
Date: Wed, 13 Mar 2024 01:30:29 +0000
References: <20240308010834.4023772-1-chao@kernel.org>
In-Reply-To: <20240308010834.4023772-1-chao@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
 linux-f2fs-devel@lists.sourceforge.net

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