From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: pbonzini@redhat.com, eblake@redhat.com, den@openvz.org,
vsementsov@virtuozzo.com
Subject: [Qemu-devel] [PATCH 3/5] nbd/server: fix: check client->closing before reply sending
Date: Thu, 8 Mar 2018 21:46:34 +0300 [thread overview]
Message-ID: <20180308184636.178534-4-vsementsov@virtuozzo.com> (raw)
In-Reply-To: <20180308184636.178534-1-vsementsov@virtuozzo.com>
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
---
It's like an RFC. I'm not sure, but this place looks like a bug. Shouldn't
we chack client-closing even before nbd_client_receive_next_request() call?
nbd/server.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/nbd/server.c b/nbd/server.c
index e0de431e10..97b45a21fa 100644
--- a/nbd/server.c
+++ b/nbd/server.c
@@ -1547,10 +1547,6 @@ static coroutine_fn void nbd_trip(void *opaque)
goto disconnect;
}
- if (ret < 0) {
- goto reply;
- }
-
if (client->closing) {
/*
* The client may be closed when we are blocked in
@@ -1559,6 +1555,10 @@ static coroutine_fn void nbd_trip(void *opaque)
goto done;
}
+ if (ret < 0) {
+ goto reply;
+ }
+
switch (request.type) {
case NBD_CMD_READ:
/* XXX: NBD Protocol only documents use of FUA with WRITE */
--
2.11.1
next prev parent reply other threads:[~2018-03-08 18:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 18:46 [Qemu-devel] [PATCH 0/5] nbd server fixing and refactoring before BLOCK_STATUS Vladimir Sementsov-Ogievskiy
2018-03-08 18:46 ` [Qemu-devel] [PATCH 1/5] nbd/server: move nbd_co_send_structured_error up Vladimir Sementsov-Ogievskiy
2018-03-09 16:39 ` Eric Blake
2018-03-08 18:46 ` [Qemu-devel] [PATCH v2 2/5] nbd/server: fix sparse read Vladimir Sementsov-Ogievskiy
2018-03-09 19:55 ` Eric Blake
2018-03-08 18:46 ` Vladimir Sementsov-Ogievskiy [this message]
2018-03-09 21:51 ` [Qemu-devel] [PATCH 3/5] nbd/server: fix: check client->closing before reply sending Eric Blake
2018-03-12 21:51 ` Eric Blake
2018-03-08 18:46 ` [Qemu-devel] [PATCH 4/5] nbd/server: refactor nbd_trip: cmd_read and generic reply Vladimir Sementsov-Ogievskiy
2018-03-09 22:21 ` Eric Blake
2018-03-08 18:46 ` [Qemu-devel] [PATCH 5/5] nbd/server: refactor nbd_trip: split out nbd_handle_request Vladimir Sementsov-Ogievskiy
2018-03-09 22:29 ` Eric Blake
2018-03-09 16:41 ` [Qemu-devel] [PATCH 0/5] nbd server fixing and refactoring before BLOCK_STATUS Eric Blake
2018-03-09 16:57 ` Vladimir Sementsov-Ogievskiy
2018-03-09 19:20 ` Eric Blake
2018-03-12 22:31 ` Eric Blake
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=20180308184636.178534-4-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).