From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Liu Bo <bo.li.liu@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: use self-explaining variable
Date: Sat, 23 Sep 2017 08:46:55 +0800 [thread overview]
Message-ID: <4d9fe9dd-ccde-964c-ea88-bce4eeafc81a@gmx.com> (raw)
In-Reply-To: <20170922233618.20034-1-bo.li.liu@oracle.com>
On 2017年09月23日 07:36, Liu Bo wrote:
> This uses a bool 'do_backup' to help understand this piece of code.
>
> Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> ---
> This is based on a patch "Btrfs: do not backup tree roots when fsync".
>
> fs/btrfs/disk-io.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index cdb7043..9811b9d 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -3691,6 +3691,7 @@ int write_all_supers(struct btrfs_fs_info *fs_info, int max_mirrors)
> int max_errors;
> int total_errors = 0;
> u64 flags;
> + bool do_backup = (max_mirrors == 0);
Why not replacing @max_mirrors with @do_backup as parameter?
Thanks,
Qu
>
> do_barriers = !btrfs_test_opt(fs_info, NOBARRIER);
>
> @@ -3699,7 +3700,7 @@ int write_all_supers(struct btrfs_fs_info *fs_info, int max_mirrors)
> * not from fsync where the tree roots in fs_info have not
> * been consistent on disk.
> */
> - if (max_mirrors == 0)
> + if (do_backup)
> backup_super_roots(fs_info);
>
> sb = fs_info->super_for_commit;
>
next prev parent reply other threads:[~2017-09-23 0:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 18:25 [PATCH] Btrfs: do not backup tree roots when fsync Liu Bo
2017-09-14 1:55 ` Qu Wenruo
2017-09-14 12:49 ` David Sterba
2017-09-15 21:09 ` Liu Bo
2017-09-22 23:36 ` [PATCH] Btrfs: use self-explaining variable Liu Bo
2017-09-23 0:46 ` Qu Wenruo [this message]
2017-09-23 0:48 ` Liu Bo
2017-09-23 1:09 ` Qu Wenruo
2017-09-24 13:24 ` 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=4d9fe9dd-ccde-964c-ea88-bce4eeafc81a@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=bo.li.liu@oracle.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).