From: "zhangwensheng (E)" <zhangwensheng5@huawei.com>
To: <josef@toxicpanda.com>, <axboe@kernel.dk>
Cc: <linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<nbd@other.debian.org>, <yukuai3@huawei.com>
Subject: Re: [PATCH -next] nbd: fix possible overflow on 'first_minor' in nbd_dev_add()
Date: Thu, 17 Mar 2022 21:05:11 +0800 [thread overview]
Message-ID: <8139ea99-09fa-eb84-e9ef-f1fb470b5b88@huawei.com> (raw)
In-Reply-To: <0e5faf35-5adb-3ea1-9f7f-7c4f61a623b2@huawei.com>
friendly ping...
在 2022/3/11 10:43, zhangwensheng (E) 写道:
> friendly ping...
>
> 在 2022/3/10 17:32, Zhang Wensheng 写道:
>> When 'index' is a big numbers, it may become negative which forced
>> to 'int'. then 'index << part_shift' might overflow to a positive
>> value that is not greater than '0xfffff', then sysfs might complains
>> about duplicate creation. Because of this, move the 'index' judgment
>> to the front will fix it and be better.
>>
>> Fixes: b0d9111a2d53 ("nbd: use an idr to keep track of nbd devices")
>> Fixes: 940c264984fd ("nbd: fix possible overflow for 'first_minor' in
>> nbd_dev_add()")
>> Signed-off-by: Zhang Wensheng <zhangwensheng5@huawei.com>
>> ---
>> drivers/block/nbd.c | 24 ++++++++++++------------
>> 1 file changed, 12 insertions(+), 12 deletions(-)
>>
>> diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
>> index 5a1f98494ddd..b3cdfc0ffb98 100644
>> --- a/drivers/block/nbd.c
>> +++ b/drivers/block/nbd.c
>> @@ -1800,17 +1800,6 @@ static struct nbd_device *nbd_dev_add(int
>> index, unsigned int refs)
>> refcount_set(&nbd->refs, 0);
>> INIT_LIST_HEAD(&nbd->list);
>> disk->major = NBD_MAJOR;
>> -
>> - /* Too big first_minor can cause duplicate creation of
>> - * sysfs files/links, since index << part_shift might overflow, or
>> - * MKDEV() expect that the max bits of first_minor is 20.
>> - */
>> - disk->first_minor = index << part_shift;
>> - if (disk->first_minor < index || disk->first_minor > MINORMASK) {
>> - err = -EINVAL;
>> - goto out_free_work;
>> - }
>> -
>> disk->minors = 1 << part_shift;
>> disk->fops = &nbd_fops;
>> disk->private_data = nbd;
>> @@ -1915,8 +1904,19 @@ static int nbd_genl_connect(struct sk_buff
>> *skb, struct genl_info *info)
>> if (!netlink_capable(skb, CAP_SYS_ADMIN))
>> return -EPERM;
>> - if (info->attrs[NBD_ATTR_INDEX])
>> + if (info->attrs[NBD_ATTR_INDEX]) {
>> index = nla_get_u32(info->attrs[NBD_ATTR_INDEX]);
>> +
>> + /*
>> + * Too big first_minor can cause duplicate creation of
>> + * sysfs files/links, since index << part_shift might
>> overflow, or
>> + * MKDEV() expect that the max bits of first_minor is 20.
>> + */
>> + if (index < 0 || index > MINORMASK >> part_shift) {
>> + printk(KERN_ERR "nbd: illegal input index %d\n", index);
>> + return -EINVAL;
>> + }
>> + }
>> if (!info->attrs[NBD_ATTR_SOCKETS]) {
>> printk(KERN_ERR "nbd: must specify at least one socket\n");
>> return -EINVAL;
> .
next prev parent reply other threads:[~2022-03-17 13:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 9:32 Zhang Wensheng
2022-03-11 2:43 ` zhangwensheng (E)
2022-03-17 13:05 ` zhangwensheng (E) [this message]
2022-03-31 0:45 ` zhangwensheng (E)
2022-03-31 14:07 ` Josef Bacik
2022-03-31 14:30 ` Jens Axboe
2022-04-06 11:24 Zhang Wensheng
2022-04-06 12:55 ` Jens Axboe
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=8139ea99-09fa-eb84-e9ef-f1fb470b5b88@huawei.com \
--to=zhangwensheng5@huawei.com \
--cc=axboe@kernel.dk \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=yukuai3@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®