From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Naohiro Aota <naohiro.aota@wdc.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: zoned: disable space cache using proper function
Date: Fri, 14 May 2021 17:30:49 +0200 [thread overview]
Message-ID: <20210514153049.GZ7604@twin.jikos.cz> (raw)
In-Reply-To: <275c2c31-c8e4-cf9e-9137-483efd3e1efa@gmx.com>
On Fri, May 14, 2021 at 06:05:05PM +0800, Qu Wenruo wrote:
>
>
> On 2021/5/14 上午10:03, Naohiro Aota wrote:
> > As btrfs_set_free_space_cache_v1_active() is introduced, this patch uses
> > it to disable space cache v1 properly.
> >
> > Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
> > ---
> > fs/btrfs/super.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
> > index 4a396c1147f1..89ffc17d074c 100644
> > --- a/fs/btrfs/super.c
> > +++ b/fs/btrfs/super.c
> > @@ -592,7 +592,7 @@ int btrfs_parse_options(struct btrfs_fs_info *info, char *options,
> > if (btrfs_is_zoned(info)) {
> > btrfs_info(info,
> > "zoned: clearing existing space cache");
> > - btrfs_set_super_cache_generation(info->super_copy, 0);
> > + btrfs_set_free_space_cache_v1_active(info, false);
>
> Can we have a better naming?
>
> The set_..._active() really looks like to *enable* space cache, other
> than disabling it.
Agreed, it's really confusing and does the opposite of the name, this
needs fixing.
next prev parent reply other threads:[~2021-05-14 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 2:03 [PATCH] btrfs: zoned: disable space cache using proper function Naohiro Aota
2021-05-14 10:05 ` Qu Wenruo
2021-05-14 15:30 ` David Sterba [this message]
2021-05-18 6:13 ` Naohiro Aota
2021-05-14 15:27 ` David Sterba
2021-05-18 6:21 ` Naohiro Aota
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=20210514153049.GZ7604@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=quwenruo.btrfs@gmx.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.