public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Sun YangKai <sunk67188@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3] btrfs: fix nonzero lowest level handling in btrfs_search_forward()
Date: Thu, 12 Jun 2025 23:51:01 +0800	[thread overview]
Message-ID: <6166825.lOV4Wx5bFT@saltykitkat> (raw)
In-Reply-To: <20250612083522.24878-1-sunk67188@gmail.com>

> Commit 323ac95bce44 ("Btrfs: don't read leaf blocks containing only
> checksums during truncate") changed the condition from `level == 0` to
> `level == path->lowest_level`, while its origional purpose is just to do
> some leaf nodes handling (calling btrfs_item_key_to_cpu()) and skip some
> code that doesn't fit leaf nodes.
> 
> After changing the condition, the code path
> 1. also handle the non-leaf nodes when path->lowest_level is nonzero,
>    which is wrong. However, it seems that btrfs_search_forward() is never
>    called with a nonzero path->lowest_level, which makes this bug not
>    found before.
> 2. makes the later if block with the same condition, which is origionally
>    used to handle non-leaf node (calling btrfs_node_key_to_cpu()) when
>    lowest_level is not zero, dead code.
> 
> This changes the behavior when btrfs_search_forward() is called with
> nonzero path->lowest_level. But this never happens in the current code
> base, and the previous behavior is wrong. So the change of behavior will
> not be a problem.
> 
> Fix: commit 323ac95bce44 ("Btrfs: don't read leaf blocks containing only
> checksums during truncate") Signed-off-by: Sun YangKai
> <sunk67188@gmail.com>
> ---
>  fs/btrfs/ctree.c | 18 +++++-------------
>  1 file changed, 5 insertions(+), 13 deletions(-)
> 
> diff --git a/fs/btrfs/ctree.c b/fs/btrfs/ctree.c
> index a2e7979372cc..56a49d85b2a4 100644
> --- a/fs/btrfs/ctree.c
> +++ b/fs/btrfs/ctree.c
> @@ -4585,16 +4585,13 @@ int btrfs_del_items(struct btrfs_trans_handle
> *trans, struct btrfs_root *root,
> 
>  /*
>   * A helper function to walk down the tree starting at min_key, and looking
> - * for nodes or leaves that are have a minimum transaction id.
> + * for leaves that are have a minimum transaction id.
>   * This is used by the btree defrag code, and tree logging
>   *
>   * This does not cow, but it does stuff the starting key it finds back
>   * into min_key, so you can call btrfs_search_slot with cow=1 on the
>   * key and get a writable path.
>   *
> - * This honors path->lowest_level to prevent descent past a given level
> - * of the tree.
> - *
>   * min_trans indicates the oldest transaction that you are interested
>   * in walking through.  Any nodes or leaves older than min_trans are
>   * skipped over (without reading them).
> @@ -4615,6 +4612,7 @@ int btrfs_search_forward(struct btrfs_root *root,
> struct btrfs_key *min_key, int keep_locks = path->keep_locks;
> 
>  	ASSERT(!path->nowait);
> +	ASSERT(path->lowest_level == 0);
>  	path->keep_locks = 1;
>  again:
>  	cur = btrfs_read_lock_root_node(root);
> @@ -4636,8 +4634,8 @@ int btrfs_search_forward(struct btrfs_root *root,
> struct btrfs_key *min_key, goto out;
>  		}
> 
> -		/* at the lowest level, we're done, setup the path and exit */
> -		if (level == path->lowest_level) {
> +		/* at the level 0, we're done, setup the path and exit */
> +		if (level == 0) {
>  			if (slot >= nritems)
>  				goto find_next_key;
>  			ret = 0;
> @@ -4678,12 +4676,6 @@ int btrfs_search_forward(struct btrfs_root *root,
> struct btrfs_key *min_key, goto out;
>  			}
>  		}
> -		if (level == path->lowest_level) {
> -			ret = 0;
> -			/* Save our key for returning back. */
> -			btrfs_node_key_to_cpu(cur, min_key, slot);
> -			goto out;
> -		}
>  		cur = btrfs_read_node_slot(cur, slot);
>  		if (IS_ERR(cur)) {
>  			ret = PTR_ERR(cur);
> @@ -4699,7 +4691,7 @@ int btrfs_search_forward(struct btrfs_root *root,
> struct btrfs_key *min_key, out:
>  	path->keep_locks = keep_locks;
>  	if (ret == 0)
> -		btrfs_unlock_up_safe(path, path->lowest_level + 1);
> +		btrfs_unlock_up_safe(path, 1);
>  	return ret;
>  }

This patch is suggest by Qu Wenruo.
Should I add a line like
Suggest-by: Qu Wenruo <wqu@suse.com>




  reply	other threads:[~2025-06-12 15:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12  8:32 [PATCH v3] btrfs: fix nonzero lowest level handling in btrfs_search_forward() Sun YangKai
2025-06-12 15:51 ` Sun YangKai [this message]
2025-06-18 14:49 ` Filipe Manana

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=6166825.lOV4Wx5bFT@saltykitkat \
    --to=sunk67188@gmail.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