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 3/6] nbd: remove queue freeze in nbd_add_socket
Date: Wed, 22 Jul 2026 17:20:53 +0800 [thread overview]
Message-ID: <45240cc5-1af3-40b3-93bf-7185ac4d0d55@huawei.com> (raw)
In-Reply-To: <b49d2daf-aae9-4642-9b45-7efc1d0981fc@huawei.com>
在 2026/7/22 16:45, yangerkun 写道:
>
>
> 在 2026/7/22 14:35, yu kuai 写道:
>> Hi,
>>
>> 在 2026/7/22 11:17, yu kuai 写道:
>>> Hi,
>>>
>>> 在 2026/7/13 14:56, Yang Erkun 写道:
>>>> nbd_add_socket can never run concurrently with inflight I/O:
>>>>
>>>> - netlink path: nbd_genl_connect calls nbd_add_socket before
>>>> nbd_start_device, so no I/O can happened when invoking
>>>> nbd_add_socket,
>>>> nbd_genl_reconfigure cannot too since it won't call
>>>> nbd_add_socket
>>>>
>>>> - ioctl path: NBD_SET_SOCK cannot be called after NBD_DO_IT with
>>>> the previous commit, so capability of nbd will keep 0 while
>>>> invoking NBD_SET_SOCK
>>>>
>>>> Removing the freeze in nbd_add_socket to speed up nbd device startup.
>>> Check nbd_open(), the pid is not checked there, which means the nbd
>>> device
>>> can be opened after add_disk() succeed. Normally read/write IO will
>>> not pass
>>> bio_check_eod() checking, however, there can be special zero sized
>>> bio that
>>> might still be issued to nbd device. So I think there should be a pid
>>> checking
>>> in nbd_open() for this patch, and I'm not aware of any special IO
>>> mush be handled
>>> before nbd_start_device(). Otherwise, the freeze is still necessary
>>> since
>>> nbd_handle_cmd() will deference config->socks[] directly.
>>
>> Sorry this is a mistake, nbd_open() must succeed before pid is set,
>> because of ioctl
>> like NBD_SET_SOCK and NED_DO_IT :( I just forgot this simple case.
>
> nbd can only accept request from bio, so bio_check_eod will reject them
> all?
Sorry, for read/write bio, bio_check_eod will reject them, for flush
only bio, if (!bdev_write_cache(bdev)) in submit_bio_noacct will reject
it. So it seems safe here.
>
>>
>>>
>>>> Signed-off-by: Yang Erkun <yangerkun@huawei.com>
>>>> ---
>>>> drivers/block/nbd.c | 9 ---------
>>>> 1 file changed, 9 deletions(-)
>>>>
>>>> diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
>>>> index a15553ab4b97..0755b7046ed4 100644
>>>> --- a/drivers/block/nbd.c
>>>> +++ b/drivers/block/nbd.c
>>>> @@ -1272,7 +1272,6 @@ static int nbd_add_socket(struct nbd_device
>>>> *nbd, unsigned long arg,
>>>> struct socket *sock;
>>>> struct nbd_sock **socks;
>>>> struct nbd_sock *nsock;
>>>> - unsigned int memflags;
>>>> int err;
>>>> /* Arg will be cast to int, check it to avoid overflow */
>>>> @@ -1283,12 +1282,6 @@ static int nbd_add_socket(struct nbd_device
>>>> *nbd, unsigned long arg,
>>>> return err;
>>>> nbd_reclassify_socket(sock);
>>>> - /*
>>>> - * We need to make sure we don't get any errant requests while
>>>> we're
>>>> - * reallocating the ->socks array.
>>>> - */
>>>> - memflags = blk_mq_freeze_queue(nbd->disk->queue);
>>>> -
>>>> if (!netlink && !nbd->task_setup &&
>>>> !test_bit(NBD_RT_BOUND, &config->runtime_flags))
>>>> nbd->task_setup = current;
>>>> @@ -1335,12 +1328,10 @@ static int nbd_add_socket(struct nbd_device
>>>> *nbd, unsigned long arg,
>>>> INIT_WORK(&nsock->work, nbd_pending_cmd_work);
>>>> socks[config->num_connections++] = nsock;
>>>> atomic_inc(&config->live_connections);
>>>> - blk_mq_unfreeze_queue(nbd->disk->queue, memflags);
>>>> return 0;
>>>> put_socket:
>>>> - blk_mq_unfreeze_queue(nbd->disk->queue, memflags);
>>>> sockfd_put(sock);
>>>> return err;
>>>> }
>>
>
>
next prev parent reply other threads:[~2026-07-22 9:20 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
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 [this message]
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=45240cc5-1af3-40b3-93bf-7185ac4d0d55@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