From: Anand Jain <anand.jain@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: drop math for block_reserved which is block_rsv size
Date: Tue, 4 Feb 2020 20:46:04 +0800 [thread overview]
Message-ID: <a230e596-887c-51f5-8e4a-e800406774c3@oracle.com> (raw)
In-Reply-To: <f35d657a-bbee-119c-793d-9871d0fc2c65@suse.com>
On 2/4/20 7:10 PM, Nikolay Borisov wrote:
>
>
> On 4.02.20 г. 13:05 ч., Anand Jain wrote:
>> In btrfs_update_global_block_rsv the lines
>> num_bytes = block_rsv->size - block_rsv->reserved;
>> block_rsv->reserved += num_bytes;
>> imply
>> block_rsv->reserved = block_rsv->size;
>>
>> Just assign block_rsv->size to block_rsv->reserved instead of the math.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>> fs/btrfs/block-rsv.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/btrfs/block-rsv.c b/fs/btrfs/block-rsv.c
>> index 6dacde9a7e93..62e0885c1e5d 100644
>> --- a/fs/btrfs/block-rsv.c
>> +++ b/fs/btrfs/block-rsv.c
>> @@ -304,9 +304,9 @@ void btrfs_update_global_block_rsv(struct btrfs_fs_info *fs_info)
>>
>> if (block_rsv->reserved < block_rsv->size) {
>> num_bytes = block_rsv->size - block_rsv->reserved;
>> - block_rsv->reserved += num_bytes;
>> btrfs_space_info_update_bytes_may_use(fs_info, sinfo,
>> num_bytes);
>> + block_rsv->reserved = block_rsv->size;
>
> Any particular reason why you put the assignment after
> btrfs_space_info_update_bytes_may_use and not before?
Oh. To make it similar to the else if part below.
Thanks.
>> } else if (block_rsv->reserved > block_rsv->size) {
>> num_bytes = block_rsv->reserved - block_rsv->size;
>> btrfs_space_info_update_bytes_may_use(fs_info, sinfo,
>>
next prev parent reply other threads:[~2020-02-04 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 11:05 [PATCH] btrfs: drop math for block_reserved which is block_rsv size Anand Jain
2020-02-04 11:10 ` Nikolay Borisov
2020-02-04 12:46 ` Anand Jain [this message]
2020-02-24 19:08 ` David Sterba
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=a230e596-887c-51f5-8e4a-e800406774c3@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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