public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Sun YangKai <sunk67188@gmail.com>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.cz
Subject: Re: [PATCH v3] btrfs: remove nonzero lowest level handling in btrfs_search_forward()
Date: Sun, 18 May 2025 20:55:48 +0930	[thread overview]
Message-ID: <fd6b96af-7376-4008-9a76-7b2a0e050fef@suse.com> (raw)
In-Reply-To: <20250517134723.25843-1-sunk67188@gmail.com>



在 2025/5/17 23:17, Sun YangKai 写道:
> 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.
> 
> Considering this function is never called with a nonzero
> path->lowest_path for years and the code handling this case is wrongly
> implemented, the path->lowest_level related logic is fully removed.



> 
> Related dead codes are also removed, and related goto logic is replaced
> with if conditions, which makes the code easier to read for new comers.
> 
> This changes the behavior when btrfs_search_forward() is called with
> nonzero path->lowest_level: now we will get a warning, and still use
> 0 as lowest_level. But since this never happens in the current codebase,
> and the previous behavior is wrong. So the behavior change of behavior
> will not be a problem.
> 
> The bevavior of the function called with a zero path->lowest_level, which
> is acturally how this function is used in current codebase, should be the
> same with previous version.
> 
> 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 | 58 ++++++++++++++++++++++--------------------------
>   1 file changed, 26 insertions(+), 32 deletions(-)
> 
> diff --git a/fs/btrfs/ctree.c b/fs/btrfs/ctree.c
> index a2e7979372cc..32844277f2cd 100644
> --- a/fs/btrfs/ctree.c
> +++ b/fs/btrfs/ctree.c
> @@ -4592,8 +4592,9 @@ int btrfs_del_items(struct btrfs_trans_handle *trans, struct btrfs_root *root,
>    * 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.
> + * This does not honor path->lowest_level any more because this
> + * function is never called with a nonzero path->lowest_level and the
> + * implementation of handling it in this function is broken for years.
This part is not helpful.

Saying something like "path->lowest_level must be 0" is more than enough.

>    *
>    * min_trans indicates the oldest transaction that you are interested
>    * in walking through.  Any nodes or leaves older than min_trans are
> @@ -4615,6 +4616,7 @@ int btrfs_search_forward(struct btrfs_root *root, struct btrfs_key *min_key,
>   	int keep_locks = path->keep_locks;
>   
>   	ASSERT(!path->nowait);
> +	WARN_ON(path->lowest_level > 0);

For sanity check, ASSERT() is more useful, it crashes debug kernels 
early for developers.

And of course, you have to run full fstests with CONFIG_BTRFS_ASSERT 
enbaled to make sure the new ASSERT() is not triggered.


>   	path->keep_locks = 1;
>   again:
>   	cur = btrfs_read_lock_root_node(root);
> @@ -4636,38 +4638,29 @@ 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) {

Why not just change path->lowest_level to 0 here?

You now put the (level > 0) handling into a more complex block, which 
doesn't make much sense to me, as your purpose is to reject non-zero 
lowest_level for this function.

The diff looks way more complex than it should be.

If you want to further cleanup the code, please send out a dedicated 
patch after adding the  ASSERT() and simple "path->lowest_level"->"0" 
change (and remove the "level == path->lowest_level" check after 
find_next_key: tag).

Thanks,
Qu

> -			if (slot >= nritems)
> -				goto find_next_key;
> -			ret = 0;
> -			path->slots[level] = slot;
> -			/* Save our key for returning back. */
> -			btrfs_item_key_to_cpu(cur, min_key, slot);
> -			goto out;
> -		}
> -		if (sret && slot > 0)
> -			slot--;
> -		/*
> -		 * check this node pointer against the min_trans parameters.
> -		 * If it is too old, skip to the next one.
> -		 */
> -		while (slot < nritems) {
> -			u64 gen;
> -
> -			gen = btrfs_node_ptr_generation(cur, slot);
> -			if (gen < min_trans) {
> +		if (level > 0) {
> +			/*
> +			 * Not at the lowest level and not a perfect match,
> +			 * go one slot back if possible to search lower level.
> +			 */
> +			if (sret && slot > 0)
> +				slot--;
> +			/*
> +			 * Check this node pointer against the min_trans parameters.
> +			 * If it is too old, skip to the next one.
> +			 */
> +			while (slot < nritems) {
> +				if (btrfs_node_ptr_generation(cur, slot) >= min_trans)
> +					break;
>   				slot++;
> -				continue;
>   			}
> -			break;
>   		}
> -find_next_key:
> +
> +		path->slots[level] = slot;
>   		/*
> -		 * we didn't find a candidate key in this node, walk forward
> -		 * and find another one
> +		 * We didn't find a candidate key in this node, walk forward
> +		 * and find another one.
>   		 */
> -		path->slots[level] = slot;
>   		if (slot >= nritems) {
>   			sret = btrfs_find_next_key(root, path, min_key, level,
>   						  min_trans);
> @@ -4678,12 +4671,13 @@ int btrfs_search_forward(struct btrfs_root *root, struct btrfs_key *min_key,
>   				goto out;
>   			}
>   		}
> -		if (level == path->lowest_level) {
> +		/* At the lowest level, we're done. Set the key and exit. */
> +		if (level == 0) {
>   			ret = 0;
> -			/* Save our key for returning back. */
> -			btrfs_node_key_to_cpu(cur, min_key, slot);
> +			btrfs_item_key_to_cpu(cur, min_key, slot);
>   			goto out;
>   		}
> +		/* Search down to a lower level. */
>   		cur = btrfs_read_node_slot(cur, slot);
>   		if (IS_ERR(cur)) {
>   			ret = PTR_ERR(cur);


  reply	other threads:[~2025-05-18 11:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 12:56 [PATCH v2] btrfs: fix nonzero lowest level handling in btrfs_search_forward() Sun YangKai
2025-04-29  6:57 ` Sun YangKai
2025-04-29 15:27   ` David Sterba
     [not found]     ` <6048084.MhkbZ0Pkbq@saltykitkat>
2025-05-17 13:33       ` Sun YangKai
2025-05-17 13:47         ` [PATCH v3] btrfs: remove " Sun YangKai
2025-05-18 11:25           ` Qu Wenruo [this message]
     [not found]         ` <12674804.O9o76ZdvQC@saltykitkat>
     [not found]           ` <4d02fad5-07b2-47b6-9e18-30f45bc67163@suse.com>
     [not found]             ` <5890818.DvuYhMxLoT@saltykitkat>
2025-05-19  5:30               ` Qu Wenruo

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=fd6b96af-7376-4008-9a76-7b2a0e050fef@suse.com \
    --to=wqu@suse.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sunk67188@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox