linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to update user block counts in block_operations()
Date: Tue, 25 Jun 2024 09:14:33 +0800	[thread overview]
Message-ID: <f0adf39a-5c07-49bd-910d-eebbc5f41dc1@kernel.org> (raw)
In-Reply-To: <ZnmylaqsdF65PVDp@google.com>

On 2024/6/25 1:53, Jaegeuk Kim wrote:
> On 06/06, Chao Yu wrote:
>> Commit 59c9081bc86e ("f2fs: allow write page cache when writting cp")
>> allows write() to write data to page cache during checkpoint, so block
>> count fields like .total_valid_block_count, .alloc_valid_block_count
>> and .rf_node_block_count may encounter race condition as below:
>>
>> CP				Thread A
>> - write_checkpoint
>>   - block_operations
>>    - f2fs_down_write(&sbi->node_change)
>>    - __prepare_cp_block
>>    : ckpt->valid_block_count = .total_valid_block_count
>>    - f2fs_up_write(&sbi->node_change)
>> 				- write
>> 				 - f2fs_preallocate_blocks
>> 				  - f2fs_map_blocks(,F2FS_GET_BLOCK_PRE_AIO)
>> 				   - f2fs_map_lock
>> 				    - f2fs_down_read(&sbi->node_change)
>> 				   - f2fs_reserve_new_blocks
>> 				    - inc_valid_block_count
>> 				    : percpu_counter_add(&sbi->alloc_valid_block_count, count)
>> 				    : sbi->total_valid_block_count += count
>> 				    - f2fs_up_read(&sbi->node_change)
>>   - do_checkpoint
>>   : sbi->last_valid_block_count = sbi->total_valid_block_count
>>   : percpu_counter_set(&sbi->alloc_valid_block_count, 0)
>>   : percpu_counter_set(&sbi->rf_node_block_count, 0)
>> 				- fsync
>> 				 - need_do_checkpoint
>> 				  - f2fs_space_for_roll_forward
>> 				  : alloc_valid_block_count was reset to zero,
>> 				    so, it may missed last data during checkpoint
>>
>> Let's change to update .total_valid_block_count, .alloc_valid_block_count
>> and .rf_node_block_count in block_operations(), then their access can be
>> protected by .node_change and .cp_rwsem lock, so that it can avoid above
>> race condition.
>>
>> Fixes: 59c9081bc86e ("f2fs: allow write page cache when writting cp")
>> Cc: Yunlei He <heyunlei@oppo.com>
>> Signed-off-by: Chao Yu <chao@kernel.org>
>> ---
>>   fs/f2fs/checkpoint.c | 11 ++++++-----
>>   1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
>> index 66eaad591b60..010bbd5af211 100644
>> --- a/fs/f2fs/checkpoint.c
>> +++ b/fs/f2fs/checkpoint.c
>> @@ -1298,6 +1298,12 @@ static int block_operations(struct f2fs_sb_info *sbi)
>>   	 * dirty node blocks and some checkpoint values by block allocation.
>>   	 */
>>   	__prepare_cp_block(sbi);
>> +
>> +	/* update user_block_counts */
>> +	sbi->last_valid_block_count = sbi->total_valid_block_count;
>> +	percpu_counter_set(&sbi->alloc_valid_block_count, 0);
>> +	percpu_counter_set(&sbi->rf_node_block_count, 0);
> 
> Need to add this in __prepare_cp_block()?

Fine to me, will update in v2.

Thanks,

> 
>> +
>>   	f2fs_up_write(&sbi->node_change);
>>   	return err;
>>   }
>> @@ -1575,11 +1581,6 @@ static int do_checkpoint(struct f2fs_sb_info *sbi, struct cp_control *cpc)
>>   		start_blk += NR_CURSEG_NODE_TYPE;
>>   	}
>>   
>> -	/* update user_block_counts */
>> -	sbi->last_valid_block_count = sbi->total_valid_block_count;
>> -	percpu_counter_set(&sbi->alloc_valid_block_count, 0);
>> -	percpu_counter_set(&sbi->rf_node_block_count, 0);
>> -
>>   	/* Here, we have one bio having CP pack except cp pack 2 page */
>>   	f2fs_sync_meta_pages(sbi, META, LONG_MAX, FS_CP_META_IO);
>>   	/* Wait for all dirty meta pages to be submitted for IO */
>> -- 
>> 2.40.1
>>


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2024-06-25  1:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06  9:54 [f2fs-dev] [PATCH] f2fs: fix to update user block counts in block_operations() Chao Yu
2024-06-24 17:53 ` Jaegeuk Kim
2024-06-25  1:14   ` Chao Yu [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=f0adf39a-5c07-49bd-910d-eebbc5f41dc1@kernel.org \
    --to=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 NNTP newsgroup(s).