From: David Sterba <dsterba@suse.cz>
To: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs: fix free space calculation in dump_space_info()
Date: Mon, 4 Jul 2016 19:10:25 +0200 [thread overview]
Message-ID: <20160704171025.GL13336@twin.jikos.cz> (raw)
In-Reply-To: <20160629051216.16876-1-wangxg.fnst@cn.fujitsu.com>
On Wed, Jun 29, 2016 at 01:12:16PM +0800, Wang Xiaoguang wrote:
Can you please describe in more detail what is this patch fixing?
> Signed-off-by: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
> ---
> fs/btrfs/extent-tree.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> index 8550a0e..520ba8f 100644
> --- a/fs/btrfs/extent-tree.c
> +++ b/fs/btrfs/extent-tree.c
> @@ -7747,8 +7747,8 @@ static void dump_space_info(struct btrfs_space_info *info, u64 bytes,
> printk(KERN_INFO "BTRFS: space_info %llu has %llu free, is %sfull\n",
> info->flags,
> info->total_bytes - info->bytes_used - info->bytes_pinned -
> - info->bytes_reserved - info->bytes_readonly,
> - (info->full) ? "" : "not ");
> + info->bytes_reserved - info->bytes_readonly -
> + info->bytes_may_use, (info->full) ? "" : "not ");
> printk(KERN_INFO "BTRFS: space_info total=%llu, used=%llu, pinned=%llu, "
> "reserved=%llu, may_use=%llu, readonly=%llu\n",
> info->total_bytes, info->bytes_used, info->bytes_pinned,
> --
> 2.9.0
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-07-04 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 5:12 [PATCH 2/2] btrfs: fix free space calculation in dump_space_info() Wang Xiaoguang
2016-07-04 17:10 ` David Sterba [this message]
2016-07-06 10:16 ` Wang Xiaoguang
2016-07-08 14:28 ` David Sterba
2016-07-11 11:27 ` Wang Xiaoguang
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=20160704171025.GL13336@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangxg.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).