From: Nikolay Borisov <nborisov@suse.com>
To: Liu Shixin <liushixin2@huawei.com>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: fix match incorrectly in dev_args_match_device
Date: Thu, 3 Nov 2022 10:20:32 +0200 [thread overview]
Message-ID: <357d9e4e-a975-7198-a496-1832d1ade3e9@suse.com> (raw)
In-Reply-To: <20221103083301.626561-1-liushixin2@huawei.com>
On 3.11.22 г. 10:33 ч., Liu Shixin wrote:
> syzkaller found an assert failed:
>
> assertion failed: (args->devid != (u64)-1) || args->missing, in fs/btrfs/volumes.c:6921
>
> This can be trigger when we set devid to (u64)-1) by ioctl. In this case,
> the match of devid will be skipped and the match of device may be succeed
> incorrectly.
>
> Patch 562d7b1512f7 introduced this function which is used to match device.
> This function contaions two matching scenarios, we can distinguish them by
> checking the value of args->missing rather than check whether args->devid
> and args->uuid is default value.
>
> Reported-by: syzbot+031687116258450f9853@syzkaller.appspotmail.com
> Fixes: 562d7b1512f7 ("btrfs: handle device lookup with btrfs_dev_lookup_args")
> Signed-off-by: Liu Shixin <liushixin2@huawei.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
> ---
> fs/btrfs/volumes.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index 94ba46d57920..bf2d886cfb4b 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -6918,18 +6918,18 @@ static bool dev_args_match_fs_devices(const struct btrfs_dev_lookup_args *args,
> static bool dev_args_match_device(const struct btrfs_dev_lookup_args *args,
> const struct btrfs_device *device)
> {
> - ASSERT((args->devid != (u64)-1) || args->missing);
> + if (args->missing) {
> + if (test_bit(BTRFS_DEV_STATE_IN_FS_METADATA, &device->dev_state) &&
> + !device->bdev)
> + return true;
> + return false;
> + }
>
> - if ((args->devid != (u64)-1) && device->devid != args->devid)
> + if (device->devid != args->devid)
> return false;
> if (args->uuid && memcmp(device->uuid, args->uuid, BTRFS_UUID_SIZE) != 0)
> return false;
> - if (!args->missing)
> - return true;
> - if (test_bit(BTRFS_DEV_STATE_IN_FS_METADATA, &device->dev_state) &&
> - !device->bdev)
> - return true;
> - return false;
> + return true;
> }
>
> /*
next prev parent reply other threads:[~2022-11-03 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 8:33 Liu Shixin
2022-11-03 8:20 ` Nikolay Borisov [this message]
2022-11-03 16:33 ` 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=357d9e4e-a975-7198-a496-1832d1ade3e9@suse.com \
--to=nborisov@suse.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liushixin2@huawei.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®