linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Su Yue <l@damenly.su>
To: linux-btrfs@vger.kernel.org
Cc: l@damenly.su, Chris Murphy <lists@colorremedies.com>
Subject: Re: [PATCH] btrfs-progs: fi resize: fix false 0.00B sized output
Date: Mon, 19 Apr 2021 20:49:45 +0800	[thread overview]
Message-ID: <blaaa140.fsf@damenly.su> (raw)
In-Reply-To: <20210419124541.148269-1-l@damenly.su>


On Mon 19 Apr 2021 at 20:45, Su Yue <l@damenly.su> wrote:

> Resize to nums without sign prefix makes false output:
> Resize device id 1 (/dev/sdb1) from 298.09GiB to 0.00B
>
> The resize operation would take effect though.
>
> Fix it by handling the case if mod is 0 in check_resize_args().
>
> Issue: #307
> Reported-by: Chris Murphy <lists@colorremedies.com>
> Signed-off-by: Su Yue <l@damenly.su>
> ---
>  cmds/filesystem.c | 7 +++++++
>  1 file changed, 7 insertions(+)
>
> diff --git a/cmds/filesystem.c b/cmds/filesystem.c
> index 9e3cce687d6e..607c85a0bccc 100644
> --- a/cmds/filesystem.c
> +++ b/cmds/filesystem.c
> @@ -1158,6 +1158,13 @@ static int check_resize_args(const char 
> *amount, const char *path) {
>  		}
>  		old_size = di_args[dev_idx].total_bytes;
>
> +		/* For target sizes without '+'/'-' sign prefix(e.g. 
> 1:150g) */
> +		if (mod == 0) {
> +			new_size = diff;
> +			diff = new_size - old_size;
>

> +			mod = diff;
>
Hmmm.. diff is a u64... will send v2.
> +		}
> +
>  		if (mod < 0) {
>  			if (diff > old_size) {
>  				error("current size is %s which is smaller than 
>  %s",


      reply	other threads:[~2021-04-19 12:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 12:45 [PATCH] btrfs-progs: fi resize: fix false 0.00B sized output Su Yue
2021-04-19 12:49 ` Su Yue [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=blaaa140.fsf@damenly.su \
    --to=l@damenly.su \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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).