From: yangerkun <yangerkun@huawei.com>
To: <yukuai@fygo.io>, <josef@toxicpanda.com>, <axboe@kernel.dk>,
<hch@lst.de>
Cc: <yi.zhang@huawei.com>, <chengzhihao1@huawei.com>,
<echo.chenlin@huawei.com>, <leo.lilong@huaweicloud.com>,
<wangkefeng.wang@huawei.com>, <linux-block@vger.kernel.org>,
<nbd@other.debian.org>
Subject: Re: [PATCH v3 2/6] nbd: disallow NBD_SET_SOCK on an active device
Date: Wed, 22 Jul 2026 14:12:10 +0800 [thread overview]
Message-ID: <7e8df66e-e6f6-4be4-acc2-58fce2403ad9@huawei.com> (raw)
In-Reply-To: <9210a679-21f9-4b57-9220-6a15955c5bcf@fygo.io>
在 2026/7/22 11:03, yu kuai 写道:
> Hi,
>
> 在 2026/7/13 14:56, Yang Erkun 写道:
>> We cannot add a socket to an already running nbd device, the reconfigure
>> for netlink can only active dead socket. But for ioctl path, we can call
>> NBD_SET_SOCK after NBD_DO_IT, reject this using nbd->pid which has been
>> setted when NBD_DO_IT. Besides, it is the root cause for commit
>> b98e762e3d71 ("nbd: freeze the queue while we're adding connections").
>>
>> Signed-off-by: Yang Erkun <yangerkun@huawei.com>
>> ---
>> drivers/block/nbd.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
>> index b1a5acd57426..a15553ab4b97 100644
>> --- a/drivers/block/nbd.c
>> +++ b/drivers/block/nbd.c
>> @@ -1302,6 +1302,13 @@ static int nbd_add_socket(struct nbd_device *nbd, unsigned long arg,
>> goto put_socket;
>> }
>>
>> + if (nbd->pid) {
>> + dev_err(disk_to_dev(nbd->disk),
>> + "Cannot add socket to a running device\n");
>> + err = -EBUSY;
>> + goto put_socket;
>> + }
>
> I think the checking if fine, but I'd like to add the checking before nbd_get_socket() and
> return -EBUSY directly.
OK.
>
>> +
>> nsock = kzalloc_obj(*nsock);
>> if (!nsock) {
>> err = -ENOMEM;
>
next prev parent reply other threads:[~2026-07-22 6:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 6:56 [PATCH v3 0/6] nbd: eliminate queue freeze/unfreeze overhead in connection setup Yang Erkun
2026-07-13 6:56 ` [PATCH v3 1/6] nbd: simplify find_fallback() by removing redundant logic Yang Erkun
2026-07-13 6:56 ` [PATCH v3 2/6] nbd: disallow NBD_SET_SOCK on an active device Yang Erkun
2026-07-22 3:03 ` yu kuai
2026-07-22 6:12 ` yangerkun [this message]
2026-07-13 6:56 ` [PATCH v3 3/6] nbd: remove queue freeze in nbd_add_socket Yang Erkun
2026-07-22 3:17 ` yu kuai
2026-07-22 6:35 ` yu kuai
2026-07-22 8:45 ` yangerkun
2026-07-22 9:20 ` yangerkun
2026-07-13 6:56 ` [PATCH v3 4/6] nbd: set nr_hw_queues at device creation to skip queue freeze Yang Erkun
2026-07-22 3:38 ` yu kuai
2026-07-23 1:09 ` yangerkun
2026-07-13 6:56 ` [PATCH v3 5/6] nbd: skip queue freeze when setting size at device startup Yang Erkun
2026-07-22 3:49 ` yu kuai
2026-07-23 1:22 ` yangerkun
2026-07-13 6:56 ` [PATCH v3 6/6] nbd: add nr_hw_queues module parameter for pre-created devices Yang Erkun
2026-07-22 3:53 ` yu kuai
2026-07-23 1:24 ` yangerkun
2026-07-21 8:41 ` [PATCH v3 0/6] nbd: eliminate queue freeze/unfreeze overhead in connection setup yangerkun
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=7e8df66e-e6f6-4be4-acc2-58fce2403ad9@huawei.com \
--to=yangerkun@huawei.com \
--cc=axboe@kernel.dk \
--cc=chengzhihao1@huawei.com \
--cc=echo.chenlin@huawei.com \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=leo.lilong@huaweicloud.com \
--cc=linux-block@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=wangkefeng.wang@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai@fygo.io \
/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