All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Marcos Paulo de Souza <marcos@mpdesouza.com>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.com, nborisov@suse.com,
	wqu@suse.com
Subject: Re: [PATCH] btrfs: ioctl: resize: Only how new size if size changed
Date: Tue, 11 Feb 2020 20:34:49 +0100	[thread overview]
Message-ID: <20200211193449.GH2902@twin.jikos.cz> (raw)
In-Reply-To: <20200211135526.22793-1-marcos@mpdesouza.com>

On Tue, Feb 11, 2020 at 10:55:26AM -0300, Marcos Paulo de Souza wrote:
> There is no point to inform the user about "new size" if didn't changed
> at all.

Makes sense. I'll also update the message to show the old and new sizes.

> Signed-off-by: Marcos Paulo de Souza <marcos@mpdesouza.com>
> ---
>  fs/btrfs/ioctl.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index be5350582955..fa31a8021d24 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -1712,9 +1712,6 @@ static noinline int btrfs_ioctl_resize(struct file *file,
>  
>  	new_size = round_down(new_size, fs_info->sectorsize);
>  
> -	btrfs_info_in_rcu(fs_info, "new size for %s is %llu",
> -			  rcu_str_deref(device->name), new_size);
> -
>  	if (new_size > old_size) {
>  		trans = btrfs_start_transaction(root, 0);
>  		if (IS_ERR(trans)) {
> @@ -1727,6 +1724,9 @@ static noinline int btrfs_ioctl_resize(struct file *file,
>  		ret = btrfs_shrink_device(device, new_size);
>  	} /* equal, nothing need to do */
>  
> +	if (ret == 0 && new_size != old_size)
> +		btrfs_info_in_rcu(fs_info, "new size for %s is %llu",
> +			  rcu_str_deref(device->name), new_size);

And maybe also print devid, other messages usually print both.

>  out_free:
>  	kfree(vol_args);
>  out:
> -- 
> 2.24.0

  parent reply	other threads:[~2020-02-11 19:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 13:55 [PATCH] btrfs: ioctl: resize: Only how new size if size changed Marcos Paulo de Souza
2020-02-11 18:30 ` Johannes Thumshirn
2020-02-11 19:34 ` David Sterba [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-11 13:39 Marcos Paulo de Souza

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=20200211193449.GH2902@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marcos@mpdesouza.com \
    --cc=nborisov@suse.com \
    --cc=wqu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.