mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>,
	<stable@vger.kernel.org>
Subject: Re: [PATCH] f2fs: fix wrong bfree and bavail
Date: Wed, 6 Sep 2017 11:19:34 +0800	[thread overview]
Message-ID: <58ffa17c-286a-a7e6-8cf8-7213bfe2acf7@huawei.com> (raw)
In-Reply-To: <20170906031028.GA61332@jaegeuk-macbookpro.roam.corp.google.com>

On 2017/9/6 11:10, Jaegeuk Kim wrote:
> On 09/06, Chao Yu wrote:
>> On 2017/9/6 5:06, Jaegeuk Kim wrote:
>>> This patch fixes bavail and bfree finally.
>>>
>>> long    f_bfree;    /* free blocks in fs */
>>> long    f_bavail;   /* free blocks avail to non-superuser */
>>>
>>> So, bfree represents all the reserved blocks, while bavail does the space only
>>> visible to normal user.
>>>
>>> Fix: 3e6d0b4d9c1c ("f2fs: fix incorrect f_bfree calculation in ->statfs")
>>> Cc: <stable@vger.kernel.org> # 4.8+
>>> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
>>> ---
>>>  fs/f2fs/super.c | 4 ++--
>>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
>>> index 7e29db227910..17cca4cb93af 100644
>>> --- a/fs/f2fs/super.c
>>> +++ b/fs/f2fs/super.c
>>> @@ -955,8 +955,8 @@ static int f2fs_statfs(struct dentry *dentry, struct kstatfs *buf)
>>>  	buf->f_bsize = sbi->blocksize;
>>>  
>>>  	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) -
>>> +	buf->f_bfree = user_block_count - valid_user_blocks(sbi);
>>> +	buf->f_bavail = user_block_count - valid_user_blocks(sbi) - ovp_count -
>>
>> 	set_cp(user_block_count, ((get_cp(free_segment_count) + 6 -
>> 			get_cp(overprov_segment_count)) * c.blks_per_seg));
>>
>> As we calculated in mkfs, we have removed ovp_count in user_block_count, so
>> shouldn't we add ovp_count for f_bfree here?
> 
> Hehe, I already dropped this. :P

Alright. :)

> It seems like something wrong with df in android.

Maybe its version is too old?

Thanks,

> 
>>
>> Thanks,
>>
>>>  						sbi->reserved_blocks;
>>>  
>>>  	avail_node_count = sbi->total_node_count - F2FS_RESERVED_NODE_NUM;
>>>
> 
> .
> 

      reply	other threads:[~2017-09-06  3:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 21:06 Jaegeuk Kim
2017-09-05 21:20 ` Andreas Dilger
2017-09-05 22:41   ` Jaegeuk Kim
2017-09-06  3:07 ` Chao Yu
2017-09-06  3:10   ` Jaegeuk Kim
2017-09-06  3:19     ` 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=58ffa17c-286a-a7e6-8cf8-7213bfe2acf7@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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

all inboxes | Powered by JetHome®