All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Liu Bo <obuil.liubo@gmail.com>
Cc: David Sterba <dsterba@suse.cz>, Liu Bo <bo.liu@linux.alibaba.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] Btrfs: set keep_lock when necessary in btrfs_defrag_leaves
Date: Fri, 27 Apr 2018 12:55:16 +0200	[thread overview]
Message-ID: <20180427105516.GY21272@twin.jikos.cz> (raw)
In-Reply-To: <CANQeFDBF7RwCufPa7s782fPsw60JBRq70ue_Dq7O__M0XFxaew@mail.gmail.com>

On Fri, Apr 27, 2018 at 11:23:23AM +0800, Liu Bo wrote:
> >> ---
> >> v2: update commit log with more details.
> >>
> >>  fs/btrfs/tree-defrag.c | 3 +--
> >>  1 file changed, 1 insertion(+), 2 deletions(-)
> >>
> >> diff --git a/fs/btrfs/tree-defrag.c b/fs/btrfs/tree-defrag.c
> >> index 3c0987ab587d..c12747904d4c 100644
> >> --- a/fs/btrfs/tree-defrag.c
> >> +++ b/fs/btrfs/tree-defrag.c
> >> @@ -65,8 +65,6 @@ int btrfs_defrag_leaves(struct btrfs_trans_handle *trans,
> >>               memcpy(&key, &root->defrag_progress, sizeof(key));
> >>       }
> >>
> >> -     path->keep_locks = 1;
> >> -
> >>       ret = btrfs_search_forward(root, &key, path, BTRFS_OLDEST_GENERATION);
> >
> > What does btrfs_search_forward do as the first statement:
> >
> > 5115 int btrfs_search_forward(struct btrfs_root *root, struct btrfs_key *min_key,
> > 5116                          struct btrfs_path *path,
> > 5117                          u64 min_trans)
> > 5118 {
> > .... declarations
> > 5128
> > 5129         path->keep_locks = 1;
> >
> > So even if removed from above, there will be no change. The value of
> > keep_locks is preserved after btrfs_path_release.
> >
> 
> It will set it back,
> 
> out:
>         path->keep_locks = keep_locks;

Oh, right. So much for reading the whole function.

  reply	other threads:[~2018-04-27 10:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26  1:27 [PATCH v2] Btrfs: set keep_lock when necessary in btrfs_defrag_leaves Liu Bo
2018-04-26  4:57 ` Nikolay Borisov
2018-04-26 18:06 ` David Sterba
2018-04-27  3:23   ` Liu Bo
2018-04-27 10:55     ` David Sterba [this message]
2018-04-27  5:36   ` Liu Bo
2018-05-01 13:39     ` 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=20180427105516.GY21272@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=bo.liu@linux.alibaba.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=obuil.liubo@gmail.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.