public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: relocation: Remove is_cowonly_root()
Date: Wed, 12 Feb 2020 08:00:45 -0500	[thread overview]
Message-ID: <e4dfd024-d014-b637-4d9e-7a8b1e155bbf@toxicpanda.com> (raw)
In-Reply-To: <20200212074331.32800-1-wqu@suse.com>

On 2/12/20 2:43 AM, Qu Wenruo wrote:
> This function is only used in read_fs_root(), which is just a wrapper of
> btrfs_get_fs_root().
> 
> For all the mentioned essential roots except log root tree,
> btrfs_get_fs_root() has its own quick path to grab them from fs_info
> directly, thus no need for key.offset modification.
> 
> For subvolume trees, btrfs_get_fs_root() with key.offset == -1 is
> completely fine.
> 
> For log trees and log root tree, it's impossible to hit them, as for
> relocation all backrefs are fetched from commit root, which never
> records log tree blocks.
> 
> Log tree blocks either get freed in regular transaction commit, or
> replayed at mount time. At runtime we should never hit an backref for
> log tree in extent tree.
> 
> Signed-off-by: Qu Wenruo <wqu@suse.com>

Reviewed-by: Josef Bacik <josef@toxicpanda.com>

Thanks,

Josef

  reply	other threads:[~2020-02-12 13:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12  7:43 [PATCH] btrfs: relocation: Remove is_cowonly_root() Qu Wenruo
2020-02-12 13:00 ` Josef Bacik [this message]
2020-02-14 16:38 ` 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=e4dfd024-d014-b637-4d9e-7a8b1e155bbf@toxicpanda.com \
    --to=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox