From: Yang Erkun <yangerkun@huawei.com>
To: josef@toxicpanda.com, axboe@kernel.dk, hch@lst.de, yukuai@kernel.org
Cc: yi.zhang@huawei.com, chengzhihao1@huawei.com,
echo.chenlin@huawei.com, leo.lilong@huaweicloud.com,
wangkefeng.wang@huawei.com, huawei.libin@huawei.com,
leijitang@huawei.com, linux-block@vger.kernel.org,
nbd@other.debian.org
Subject: [PATCH v7 3/8] nbd: clear queue limits on disconnect
Date: Wed, 5 Aug 2026 14:58:38 +0800 [thread overview]
Message-ID: <20260805065843.3332859-4-yangerkun@huawei.com> (raw)
In-Reply-To: <20260805065843.3332859-1-yangerkun@huawei.com>
An inactive nbd device may refuse any I/O operations. The nbd_config_put
function calls invalidate_disk, which sets the device capacity to zero
to reject all read and write I/O. For zero-sector flush I/O requests
from blkdev_issue_flush, if the write cache is disabled, the zero-sector
flush I/O immediately returns 0 in submit_bio_noacct. However, since
nbd_config_put does not clear the write cache state, an inactive nbd
device might still have the write cache enabled. In this situation,
zero-sector flush I/O will return -EIO because there is no active socket.
Additionally, BLK_FEAT_FUA and BLK_FEAT_ROTATIONAL flags may also remain
stale, resetting all of them ensures consistent behavior.
The limits update uses queue_limits_commit_update() (the non-freezing
variant) because config_refs == 0 here means every fd is closed and recv
threads have drained, so no in-flight I/O can read q->limits concurrently.
Signed-off-by: Yang Erkun <yangerkun@huawei.com>
---
drivers/block/nbd.c | 43 ++++++++++++++++++++++++++-----------------
1 file changed, 26 insertions(+), 17 deletions(-)
diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
index 7ec85f94f742..78df6f459da6 100644
--- a/drivers/block/nbd.c
+++ b/drivers/block/nbd.c
@@ -331,6 +331,26 @@ static void nbd_mark_nsock_dead(struct nbd_device *nbd, struct nbd_sock *nsock,
nsock->sent = 0;
}
+static void nbd_apply_limits(struct queue_limits *lim, u32 flags)
+{
+ lim->features &= ~(BLK_FEAT_WRITE_CACHE | BLK_FEAT_FUA | BLK_FEAT_ROTATIONAL);
+ lim->max_hw_discard_sectors = 0;
+ lim->max_write_zeroes_sectors = 0;
+
+ if (flags & NBD_FLAG_SEND_TRIM)
+ lim->max_hw_discard_sectors = UINT_MAX >> SECTOR_SHIFT;
+ if (flags & NBD_FLAG_SEND_FLUSH) {
+ lim->features |= BLK_FEAT_WRITE_CACHE;
+ if (flags & NBD_FLAG_SEND_FUA)
+ lim->features |= BLK_FEAT_FUA;
+ }
+
+ if (flags & NBD_FLAG_ROTATIONAL)
+ lim->features |= BLK_FEAT_ROTATIONAL;
+ if (flags & NBD_FLAG_SEND_WRITE_ZEROES)
+ lim->max_write_zeroes_sectors = UINT_MAX >> SECTOR_SHIFT;
+}
+
static int nbd_set_size(struct nbd_device *nbd, loff_t bytesize, loff_t blksize)
{
struct queue_limits lim;
@@ -352,23 +372,7 @@ static int nbd_set_size(struct nbd_device *nbd, loff_t bytesize, loff_t blksize)
return 0;
lim = queue_limits_start_update(nbd->disk->queue);
- if (nbd->config->flags & NBD_FLAG_SEND_TRIM)
- lim.max_hw_discard_sectors = UINT_MAX >> SECTOR_SHIFT;
- else
- lim.max_hw_discard_sectors = 0;
- if (!(nbd->config->flags & NBD_FLAG_SEND_FLUSH)) {
- lim.features &= ~(BLK_FEAT_WRITE_CACHE | BLK_FEAT_FUA);
- } else if (nbd->config->flags & NBD_FLAG_SEND_FUA) {
- lim.features |= BLK_FEAT_WRITE_CACHE | BLK_FEAT_FUA;
- } else {
- lim.features |= BLK_FEAT_WRITE_CACHE;
- lim.features &= ~BLK_FEAT_FUA;
- }
- if (nbd->config->flags & NBD_FLAG_ROTATIONAL)
- lim.features |= BLK_FEAT_ROTATIONAL;
- if (nbd->config->flags & NBD_FLAG_SEND_WRITE_ZEROES)
- lim.max_write_zeroes_sectors = UINT_MAX >> SECTOR_SHIFT;
-
+ nbd_apply_limits(&lim, nbd->config->flags);
lim.logical_block_size = blksize;
lim.physical_block_size = blksize;
error = queue_limits_commit_update_frozen(nbd->disk->queue, &lim);
@@ -1469,8 +1473,13 @@ static void nbd_config_put(struct nbd_device *nbd)
if (refcount_dec_and_mutex_lock(&nbd->config_refs,
&nbd->config_lock)) {
struct nbd_config *config = nbd->config;
+ struct queue_limits lim;
nbd_dev_dbg_close(nbd);
invalidate_disk(nbd->disk);
+ /* reset queue limits to default */
+ lim = queue_limits_start_update(nbd->disk->queue);
+ nbd_apply_limits(&lim, 0);
+ queue_limits_commit_update(nbd->disk->queue, &lim);
if (nbd->config->bytesize)
kobject_uevent(&nbd_to_dev(nbd)->kobj, KOBJ_CHANGE);
if (test_and_clear_bit(NBD_RT_HAS_PID_FILE,
--
2.52.0
next prev parent reply other threads:[~2026-08-05 7:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 6:58 [PATCH v7 0/8] nbd: eliminate queue freeze/unfreeze overhead in connection setup Yang Erkun
2026-08-05 6:58 ` [PATCH v7 1/8] nbd: simplify find_fallback() by removing redundant logic Yang Erkun
2026-08-05 6:58 ` [PATCH v7 2/8] nbd: disallow NBD_SET_SOCK on an active device Yang Erkun
2026-08-05 6:58 ` Yang Erkun [this message]
2026-08-05 8:35 ` [PATCH v7 3/8] nbd: clear queue limits on disconnect yu kuai
2026-08-05 6:58 ` [PATCH v7 4/8] nbd: remove queue freeze in nbd_add_socket Yang Erkun
2026-08-05 8:36 ` yu kuai
2026-08-05 6:58 ` [PATCH v7 5/8] nbd: skip queue freeze when setting size at device startup Yang Erkun
2026-08-05 8:37 ` yu kuai
2026-08-05 6:58 ` [PATCH v7 6/8] nbd: factor out a nbd_genl_foreach_sock Yang Erkun
2026-08-05 8:40 ` yu kuai
2026-08-05 6:58 ` [PATCH v7 7/8] nbd: remove queue freeze for newly created nbd from netlink path Yang Erkun
2026-08-05 6:58 ` [PATCH v7 8/8] nbd: add pre_defined_connections module parameter for pre-created devices Yang Erkun
2026-08-05 8:45 ` yu kuai
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=20260805065843.3332859-4-yangerkun@huawei.com \
--to=yangerkun@huawei.com \
--cc=axboe@kernel.dk \
--cc=chengzhihao1@huawei.com \
--cc=echo.chenlin@huawei.com \
--cc=hch@lst.de \
--cc=huawei.libin@huawei.com \
--cc=josef@toxicpanda.com \
--cc=leijitang@huawei.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@kernel.org \
/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