From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: fam@euphon.net, kwolf@redhat.com, vsementsov@virtuozzo.com,
qemu-devel@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
den@openvz.org
Subject: [PATCH 1/5] block/nbd-client: drop max_block restriction from block_status
Date: Mon, 2 Mar 2020 13:05:33 +0300 [thread overview]
Message-ID: <20200302100537.29058-2-vsementsov@virtuozzo.com> (raw)
In-Reply-To: <20200302100537.29058-1-vsementsov@virtuozzo.com>
NBD spec is updated, so that max_block doesn't relate to
NBD_CMD_BLOCK_STATUS. So, drop the restriction.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
---
block/nbd.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/block/nbd.c b/block/nbd.c
index 976be76647..2a58d6b91c 100644
--- a/block/nbd.c
+++ b/block/nbd.c
@@ -1320,9 +1320,7 @@ static int coroutine_fn nbd_client_co_block_status(
NBDRequest request = {
.type = NBD_CMD_BLOCK_STATUS,
.from = offset,
- .len = MIN(MIN_NON_ZERO(QEMU_ALIGN_DOWN(INT_MAX,
- bs->bl.request_alignment),
- s->info.max_block),
+ .len = MIN(QEMU_ALIGN_DOWN(INT_MAX, bs->bl.request_alignment),
MIN(bytes, s->info.size - offset)),
.flags = NBD_CMD_FLAG_REQ_ONE,
};
--
2.21.0
next prev parent reply other threads:[~2020-03-02 10:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 10:05 [PATCH 0/5] nbd: reduce max_block restrictions Vladimir Sementsov-Ogievskiy
2020-03-02 10:05 ` Vladimir Sementsov-Ogievskiy [this message]
2020-03-02 20:53 ` [PATCH 1/5] block/nbd-client: drop max_block restriction from block_status Eric Blake
2020-03-02 10:05 ` [PATCH 2/5] block/nbd-client: drop max_block restriction from discard Vladimir Sementsov-Ogievskiy
2020-03-02 20:53 ` Eric Blake
2020-03-02 10:05 ` [PATCH 3/5] block: add max_pwrite_zeroes_no_fallback to BlockLimits Vladimir Sementsov-Ogievskiy
2020-03-13 21:07 ` Eric Blake
2020-03-24 8:32 ` Vladimir Sementsov-Ogievskiy
2020-03-31 6:52 ` Vladimir Sementsov-Ogievskiy
2020-04-01 14:09 ` Vladimir Sementsov-Ogievskiy
2020-03-02 10:05 ` [PATCH 4/5] block/io: fix bdrv_co_do_pwrite_zeroes head calculation Vladimir Sementsov-Ogievskiy
2020-03-13 21:47 ` Eric Blake
2020-03-24 9:22 ` Vladimir Sementsov-Ogievskiy
2020-03-02 10:05 ` [PATCH 5/5] block/io: auto-no-fallback for write-zeroes Vladimir Sementsov-Ogievskiy
2020-03-13 21:56 ` Eric Blake
2020-04-01 14:35 ` Vladimir Sementsov-Ogievskiy
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=20200302100537.29058-2-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).