From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"open list:Network Block Dev..." <qemu-block@nongnu.org>
Subject: [Qemu-devel] [PULL 7/9] nbd/server: refactor nbd_co_send_simple_reply parameters
Date: Sat, 14 Oct 2017 19:40:31 -0500 [thread overview]
Message-ID: <20171015004033.3248-8-eblake@redhat.com> (raw)
In-Reply-To: <20171015004033.3248-1-eblake@redhat.com>
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Pass client and buffer (*data) parameters directly, to make the function
consistent with further structured reply sending functions.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Message-Id: <20171012095319.136610-7-vsementsov@virtuozzo.com>
Signed-off-by: Eric Blake <eblake@redhat.com>
---
nbd/server.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/nbd/server.c b/nbd/server.c
index 06aeadcfbb..3fcc3d3c7c 100644
--- a/nbd/server.c
+++ b/nbd/server.c
@@ -1196,12 +1196,13 @@ static inline void set_be_simple_reply(NBDSimpleReply *reply, uint64_t error,
stq_be_p(&reply->handle, handle);
}
-static int nbd_co_send_simple_reply(NBDRequestData *req,
+static int nbd_co_send_simple_reply(NBDClient *client,
uint64_t handle,
uint32_t error,
- int len, Error **errp)
+ void *data,
+ size_t len,
+ Error **errp)
{
- NBDClient *client = req->client;
NBDSimpleReply simple_reply;
int nbd_err = system_errno_to_nbd_errno(error);
int ret;
@@ -1220,7 +1221,7 @@ static int nbd_co_send_simple_reply(NBDRequestData *req,
qio_channel_set_cork(client->ioc, true);
ret = nbd_write(client->ioc, &simple_reply, sizeof(simple_reply), errp);
if (ret == 0) {
- ret = nbd_write(client->ioc, req->data, len, errp);
+ ret = nbd_write(client->ioc, data, len, errp);
if (ret < 0) {
ret = -EIO;
}
@@ -1447,9 +1448,9 @@ reply:
local_err = NULL;
}
- if (nbd_co_send_simple_reply(req, request.handle,
+ if (nbd_co_send_simple_reply(req->client, request.handle,
ret < 0 ? -ret : 0,
- reply_data_len, &local_err) < 0)
+ req->data, reply_data_len, &local_err) < 0)
{
error_prepend(&local_err, "Failed to send reply: ");
goto disconnect;
--
2.13.6
next prev parent reply other threads:[~2017-10-15 0:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 0:40 [Qemu-devel] [PULL 0/9] NBD patches through 14 Oct Eric Blake
2017-10-15 0:40 ` [Qemu-devel] [PULL 1/9] NBD: use g_new() family of functions Eric Blake
2017-10-15 0:40 ` [Qemu-devel] [PULL 2/9] block/nbd-client: assert qiov len once in nbd_co_request Eric Blake
2017-10-15 0:40 ` [Qemu-devel] [PULL 3/9] block/nbd-client: refactor nbd_co_receive_reply Eric Blake
2017-10-15 0:40 ` [Qemu-devel] [PULL 4/9] nbd: rename some simple-request related objects to be _simple_ Eric Blake
2017-10-15 0:40 ` [Qemu-devel] [PULL 5/9] nbd/server: structurize simple reply header sending Eric Blake
2017-10-15 0:40 ` [Qemu-devel] [PULL 6/9] nbd/server: do not use NBDReply structure Eric Blake
2017-10-15 0:40 ` Eric Blake [this message]
2017-10-15 0:40 ` [Qemu-devel] [PULL 8/9] nbd/server: simplify reply transmission Eric Blake
2017-10-15 0:40 ` [Qemu-devel] [PULL 9/9] nbd: header constants indenting Eric Blake
2017-10-16 16:28 ` [Qemu-devel] [PULL 0/9] NBD patches through 14 Oct Peter Maydell
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=20171015004033.3248-8-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).