mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yunlong Song <yunlong.song@huawei.com>
To: Chao Yu <yuchao0@huawei.com>, <jaegeuk@kernel.org>,
	<chao@kernel.org>, <yunlong.song@icloud.com>
Cc: <miaoxie@huawei.com>, <bintian.wang@huawei.com>,
	<linux-fsdevel@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] f2fs: fix some cases with reserved_blocks
Date: Tue, 8 Aug 2017 14:33:45 +0800	[thread overview]
Message-ID: <0d7c0552-e9d6-ae17-6c9c-bf33b3a7d06d@huawei.com> (raw)
In-Reply-To: <5cf16cae-e6bd-13e8-7309-c975f5a27c96@huawei.com>

Does this means the reserved_blocks cannot be used by users by can be 
used by filesystem?
If it can be used by filesystem, then this cannot ensure the flash 
device really reserve the
reserved_blocks space, right? The reserved_blocks is just for users?

On 2017/8/8 14:08, Chao Yu wrote:
> On 2017/8/8 12:12, Yunlong Song wrote:
>> Signed-off-by: Yunlong Song <yunlong.song@huawei.com>
>> ---
>>   fs/f2fs/recovery.c | 3 ++-
>>   fs/f2fs/super.c    | 9 +++++----
>>   2 files changed, 7 insertions(+), 5 deletions(-)
>>
>> diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c
>> index a3d0261..e288319 100644
>> --- a/fs/f2fs/recovery.c
>> +++ b/fs/f2fs/recovery.c
>> @@ -51,7 +51,8 @@ bool space_for_roll_forward(struct f2fs_sb_info *sbi)
>>   {
>>   	s64 nalloc = percpu_counter_sum_positive(&sbi->alloc_valid_block_count);
>>   
>> -	if (sbi->last_valid_block_count + nalloc > sbi->user_block_count)
>> +	if (sbi->last_valid_block_count + nalloc +
>> +			sbi->reserved_blocks > sbi->user_block_count)
> I think we can treat reserved blocks as over-provision space in f2fs, so it
> would be safe to store invalid data (may become valid during recovery) there.
> Anyway, it OK to remain old condition judgment.
>
>>   		return false;
>>   	return true;
>>   }
>> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
>> index 4c1bdcb..c644bf5 100644
>> --- a/fs/f2fs/super.c
>> +++ b/fs/f2fs/super.c
>> @@ -946,6 +946,7 @@ static int f2fs_statfs(struct dentry *dentry, struct kstatfs *buf)
>>   	u64 id = huge_encode_dev(sb->s_bdev->bd_dev);
>>   	block_t total_count, user_block_count, start_count, ovp_count;
>>   	u64 avail_node_count;
>> +	block_t avail_user_block_count;
>>   
>>   	total_count = le64_to_cpu(sbi->raw_super->block_count);
>>   	user_block_count = sbi->user_block_count;
>> @@ -953,16 +954,16 @@ static int f2fs_statfs(struct dentry *dentry, struct kstatfs *buf)
>>   	ovp_count = SM_I(sbi)->ovp_segments << sbi->log_blocks_per_seg;
>>   	buf->f_type = F2FS_SUPER_MAGIC;
>>   	buf->f_bsize = sbi->blocksize;
>> +	avail_user_block_count = user_block_count - sbi->reserved_blocks;
>>   
>>   	buf->f_blocks = total_count - start_count;
>>   	buf->f_bfree = user_block_count - valid_user_blocks(sbi) + ovp_count;
>> -	buf->f_bavail = user_block_count - valid_user_blocks(sbi) -
>> -						sbi->reserved_blocks;
>> +	buf->f_bavail = avail_user_block_count - valid_user_blocks(sbi);
>>   
>>   	avail_node_count = sbi->total_node_count - F2FS_RESERVED_NODE_NUM;
>>   
>> -	if (avail_node_count > user_block_count) {
>> -		buf->f_files = user_block_count;
>> +	if (avail_node_count > avail_user_block_count) {
> Likewise f_blocks calculation, the f_files one doesn't need to consider
> reserved_blocks.
>
> Thanks,
>
>> +		buf->f_files = avail_user_block_count;
>>   		buf->f_ffree = buf->f_bavail;
>>   	} else {
>>   		buf->f_files = avail_node_count;
>>
>
> .
>

-- 
Thanks,
Yunlong Song

  reply	other threads:[~2017-08-08  6:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08  4:12 Yunlong Song
2017-08-08  6:08 ` Chao Yu
2017-08-08  6:33   ` Yunlong Song [this message]
2017-08-08  8:13     ` Chao Yu

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=0d7c0552-e9d6-ae17-6c9c-bf33b3a7d06d@huawei.com \
    --to=yunlong.song@huawei.com \
    --cc=bintian.wang@huawei.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miaoxie@huawei.com \
    --cc=yuchao0@huawei.com \
    --cc=yunlong.song@icloud.com \
    /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

all inboxes | Powered by JetHome®