From: Yue Haibing <yuehaibing@huawei.com>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
"clm@fb.com" <clm@fb.com>,
"josef@toxicpanda.com" <josef@toxicpanda.com>,
"dsterba@suse.com" <dsterba@suse.com>,
"mpdesouza@suse.com" <mpdesouza@suse.com>,
"gniebler@suse.com" <gniebler@suse.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] btrfs: Fix passing 0 to ERR_PTR in btrfs_search_dir_index_item()
Date: Tue, 22 Oct 2024 11:22:40 +0800 [thread overview]
Message-ID: <01b2539f-6560-baa2-d968-5675f0ff2815@huawei.com> (raw)
In-Reply-To: <7daf798c-64e1-4d22-9840-8954db354c9a@wdc.com>
On 2024/10/21 16:25, Johannes Thumshirn wrote:
> On 19.10.24 11:07, Yue Haibing wrote:
>> Return NULL instead of passing to ERR_PTR while ret is zero, this fix
>> smatch warnings:
>>
>> fs/btrfs/dir-item.c:353
>> btrfs_search_dir_index_item() warn: passing zero to 'ERR_PTR'
>>
>> Fixes: 9dcbe16fccbb ("btrfs: use btrfs_for_each_slot in btrfs_search_dir_index_item")
>> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
>> ---
>> fs/btrfs/dir-item.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/btrfs/dir-item.c b/fs/btrfs/dir-item.c
>> index 001c0c2f872c..cdb30ec7366a 100644
>> --- a/fs/btrfs/dir-item.c
>> +++ b/fs/btrfs/dir-item.c
>> @@ -350,7 +350,7 @@ btrfs_search_dir_index_item(struct btrfs_root *root, struct btrfs_path *path,
>> if (ret > 0)
>> ret = 0;
>>
>> - return ERR_PTR(ret);
>> + return ret ? ERR_PTR(ret) : NULL;
>> }
>>
>> struct btrfs_dir_item *btrfs_lookup_xattr(struct btrfs_trans_handle *trans,
>
> The only caller to this is in btrfs_unlink_subvol(), which does the
> following:
>
>
> di = btrfs_search_dir_index_item(root, path, dir_ino,
> &fname.disk_name);
> if (IS_ERR_OR_NULL(di)) {
> if (!di)
> ret = -ENOENT;
> else
> ret = PTR_ERR(di);
> btrfs_abort_transaction(trans, ret);
> goto out;
> }
>
> to do:
>
> diff --git a/fs/btrfs/dir-item.c b/fs/btrfs/dir-item.c
> index d3093eba54a5..e755228d909a 100644
> --- a/fs/btrfs/dir-item.c
> +++ b/fs/btrfs/dir-item.c
> @@ -345,10 +345,7 @@ btrfs_search_dir_index_item(struct btrfs_root
> *root, struct btrfs_path *path,
> return di;
> }
> /* Adjust return code if the key was not found in the next leaf. */
ret is output variable of btrfs_for_each_slot, that return value can be 0, if a
valid slot was found, 1 if there were no more leaves, and < 0 if there was an
error.
> - if (ret > 0)
> - ret = 0;
> -
> - return ERR_PTR(ret);
> + return ERR_PTR(-ENOENT);
This overwrite other ret code, which expecting return to upstream caller
> }
>
> struct btrfs_dir_item *btrfs_lookup_xattr(struct btrfs_trans_handle
> *trans,
> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> index 35f89d14c110..00602634db3a 100644
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -4337,11 +4337,8 @@ static int btrfs_unlink_subvol(struct
> btrfs_trans_handle *trans,
> */
> if (btrfs_ino(inode) == BTRFS_EMPTY_SUBVOL_DIR_OBJECTID) {
> di = btrfs_search_dir_index_item(root, path, dir_ino,
> &fname.disk_name);
> - if (IS_ERR_OR_NULL(di)) {
> - if (!di)
> - ret = -ENOENT;
> - else
> - ret = PTR_ERR(di);
> + if (IS_ERR(di)) {
> + ret = PTR_ERR(di);
> btrfs_abort_transaction(trans, ret);
> goto out;
> }
> This is completely untested though and needs to be re-checked if it's
> even correct.
next prev parent reply other threads:[~2024-10-22 3:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 9:23 Yue Haibing
2024-10-21 8:25 ` Johannes Thumshirn
2024-10-22 3:22 ` Yue Haibing [this message]
2024-10-22 6:37 ` Johannes Thumshirn
2024-10-22 6:53 ` Yue Haibing
2024-10-22 7:16 ` Johannes Thumshirn
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=01b2539f-6560-baa2-d968-5675f0ff2815@huawei.com \
--to=yuehaibing@huawei.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=gniebler@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpdesouza@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
all inboxes | Powered by JetHome®