From: Pavel Skripkin <paskripkin@gmail.com>
To: "yukuai (C)" <yukuai3@huawei.com>, josef@toxicpanda.com, axboe@kernel.dk
Cc: linux-block@vger.kernel.org, nbd@other.debian.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
luomeng12@huawei.com, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 0/2] nbd: fix sanity check for first_minor
Date: Thu, 21 Oct 2021 19:47:51 +0300 [thread overview]
Message-ID: <8f6f738b-2d74-1778-648a-dc62603319d0@gmail.com> (raw)
In-Reply-To: <17182476-e5bf-f493-9d9b-fedb2d9c8e1a@huawei.com>
On 10/21/21 16:13, yukuai (C) wrote:
> On 2021/10/21 20:35, Pavel Skripkin wrote:
>> On 10/21/21 15:29, Yu Kuai wrote:
>>> Yu Kuai (2):
>>> nbd: fix max value for 'first_minor'
>>> nbd: fix possible overflow for 'first_minor' in nbd_dev_add()
>>>
>>> drivers/block/nbd.c | 6 +++---
>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>
>>
>> Hi, Yu!
>>
>> Thank you for the fix, but this wrong check should be just removed,
>> since root case of wrong sysfs file creation was fixed, as Christoph
>> said [1]
>
> Hi, Pavel
>
> Thanks for your response, with the root cause fixed, patch 1 is not
> needed anymore. However, the overflow case in patch 2 is still
> possible.
>
> Does anyone plan to remove the checking?
>
Hm, I thought it was already removed, but I was wrong, I guess. Let's
see what Christoph thinks about this check.
Maybe add_disk() error handling is still not in Linus tree, I haven't
checked yet. Sysfs warnings _should_ be fixed by proper error handling,
but maybe there is another problem somewhere...
With regards,
Pavel Skripkin
prev parent reply other threads:[~2021-10-21 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 12:29 [PATCH 0/2] nbd: fix sanity check for first_minor Yu Kuai
2021-10-21 12:29 ` [PATCH 1/2] nbd: fix max value for 'first_minor' Yu Kuai
2021-10-21 12:29 ` [PATCH 2/2] nbd: fix possible overflow for 'first_minor' in nbd_dev_add() Yu Kuai
2021-10-21 12:35 ` [PATCH 0/2] nbd: fix sanity check for first_minor Pavel Skripkin
2021-10-21 13:13 ` yukuai (C)
2021-10-21 13:37 ` yukuai (C)
2021-10-25 13:41 ` yukuai (C)
2021-11-01 8:06 ` yukuai (C)
2021-10-21 16:47 ` Pavel Skripkin [this message]
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=8f6f738b-2d74-1778-648a-dc62603319d0@gmail.com \
--to=paskripkin@gmail.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luomeng12@huawei.com \
--cc=nbd@other.debian.org \
--cc=yi.zhang@huawei.com \
--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;
as well as URLs for NNTP newsgroup(s).