Blame SOURCES/kvm-nbd-server-Trace-client-noncompliance-on-unaligned-r.patch

383d26
From a3c2d291823493cd39a79e0b2a38c9af29090cf0 Mon Sep 17 00:00:00 2001
383d26
From: John Snow <jsnow@redhat.com>
383d26
Date: Mon, 6 May 2019 17:56:26 +0200
383d26
Subject: [PATCH 16/53] nbd/server: Trace client noncompliance on unaligned
383d26
 requests
383d26
383d26
RH-Author: John Snow <jsnow@redhat.com>
383d26
Message-id: <20190506175629.11079-17-jsnow@redhat.com>
383d26
Patchwork-id: 87198
383d26
O-Subject: [RHEL-7.7 qemu-kvm-rhev PATCH 16/19] nbd/server: Trace client noncompliance on unaligned requests
383d26
Bugzilla: 1692018
383d26
RH-Acked-by: Max Reitz <mreitz@redhat.com>
383d26
RH-Acked-by: Stefano Garzarella <sgarzare@redhat.com>
383d26
RH-Acked-by: Thomas Huth <thuth@redhat.com>
383d26
383d26
From: Eric Blake <eblake@redhat.com>
383d26
383d26
We've recently added traces for clients to flag server non-compliance;
383d26
let's do the same for servers to flag client non-compliance. According
383d26
to the spec, if the client requests NBD_INFO_BLOCK_SIZE, it is
383d26
promising to send all requests aligned to those boundaries.  Of
383d26
course, if the client does not request NBD_INFO_BLOCK_SIZE, then it
383d26
made no promises so we shouldn't flag anything; and because we are
383d26
willing to handle clients that made no promises (the spec allows us to
383d26
use NBD_REP_ERR_BLOCK_SIZE_REQD if we had been unwilling), we already
383d26
have to handle unaligned requests (which the block layer already does
383d26
on our behalf).  So even though the spec allows us to return EINVAL
383d26
for clients that promised to behave, it's easier to always answer
383d26
unaligned requests.  Still, flagging non-compliance can be useful in
383d26
debugging a client that is trying to be maximally portable.
383d26
383d26
Qemu as client used to have one spot where it sent non-compliant
383d26
requests: if the server sends an unaligned reply to
383d26
NBD_CMD_BLOCK_STATUS, and the client was iterating over the entire
383d26
disk, the next request would start at that unaligned point; this was
383d26
fixed in commit a39286dd when the client was taught to work around
383d26
server non-compliance; but is equally fixed if the server is patched
383d26
to not send unaligned replies in the first place (yes, qemu 4.0 as
383d26
server still has few such bugs, although they will be patched in
383d26
4.1). Fortunately, I did not find any more spots where qemu as client
383d26
was non-compliant. I was able to test the patch by using the following
383d26
hack to convince qemu-io to run various unaligned commands, coupled
383d26
with serving 512-byte alignment by intentionally omitting '-f raw' on
383d26
the server while viewing server traces.
383d26
383d26
| diff --git i/nbd/client.c w/nbd/client.c
383d26
| index 427980bdd22..1858b2aac35 100644
383d26
| --- i/nbd/client.c
383d26
| +++ w/nbd/client.c
383d26
| @@ -449,6 +449,7 @@ static int nbd_opt_info_or_go(QIOChannel *ioc, uint32_t opt,
383d26
|                  nbd_send_opt_abort(ioc);
383d26
|                  return -1;
383d26
|              }
383d26
| +            info->min_block = 1;//hack
383d26
|              if (!is_power_of_2(info->min_block)) {
383d26
|                  error_setg(errp, "server minimum block size %" PRIu32
383d26
|                             " is not a power of two", info->min_block);
383d26
383d26
Signed-off-by: Eric Blake <eblake@redhat.com>
383d26
Message-Id: <20190403030526.12258-3-eblake@redhat.com>
383d26
[eblake: address minor review nits]
383d26
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
383d26
(cherry picked from commit 6e280648d21d8c0aa8a101b62d0732cd1e608743)
383d26
Signed-off-by: John Snow <jsnow@redhat.com>
383d26
383d26
Signed-off-by: Miroslav Rezanina <mrezanin@redhat.com>
383d26
---
383d26
 nbd/server.c     | 17 ++++++++++++++++-
383d26
 nbd/trace-events |  1 +
383d26
 2 files changed, 17 insertions(+), 1 deletion(-)
383d26
383d26
diff --git a/nbd/server.c b/nbd/server.c
383d26
index 6ae2154..42f77ae 100644
383d26
--- a/nbd/server.c
383d26
+++ b/nbd/server.c
383d26
@@ -124,6 +124,8 @@ struct NBDClient {
383d26
     int nb_requests;
383d26
     bool closing;
383d26
 
383d26
+    uint32_t check_align; /* If non-zero, check for aligned client requests */
383d26
+
383d26
     bool structured_reply;
383d26
     NBDExportMetaContexts export_meta;
383d26
 
383d26
@@ -533,6 +535,7 @@ static int nbd_negotiate_handle_info(NBDClient *client, uint16_t myflags,
383d26
     bool blocksize = false;
383d26
     uint32_t sizes[3];
383d26
     char buf[sizeof(uint64_t) + sizeof(uint16_t)];
383d26
+    uint32_t check_align = 0;
383d26
 
383d26
     /* Client sends:
383d26
         4 bytes: L, name length (can be 0)
383d26
@@ -609,7 +612,7 @@ static int nbd_negotiate_handle_info(NBDClient *client, uint16_t myflags,
383d26
      * whether this is OPT_INFO or OPT_GO. */
383d26
     /* minimum - 1 for back-compat, or actual if client will obey it. */
383d26
     if (client->opt == NBD_OPT_INFO || blocksize) {
383d26
-        sizes[0] = blk_get_request_alignment(exp->blk);
383d26
+        check_align = sizes[0] = blk_get_request_alignment(exp->blk);
383d26
     } else {
383d26
         sizes[0] = 1;
383d26
     }
383d26
@@ -660,6 +663,7 @@ static int nbd_negotiate_handle_info(NBDClient *client, uint16_t myflags,
383d26
 
383d26
     if (client->opt == NBD_OPT_GO) {
383d26
         client->exp = exp;
383d26
+        client->check_align = check_align;
383d26
         QTAILQ_INSERT_TAIL(&client->exp->clients, client, next);
383d26
         nbd_export_get(client->exp);
383d26
         nbd_check_meta_export(client);
383d26
@@ -2126,6 +2130,17 @@ static int nbd_co_receive_request(NBDRequestData *req, NBDRequest *request,
383d26
         return (request->type == NBD_CMD_WRITE ||
383d26
                 request->type == NBD_CMD_WRITE_ZEROES) ? -ENOSPC : -EINVAL;
383d26
     }
383d26
+    if (client->check_align && !QEMU_IS_ALIGNED(request->from | request->len,
383d26
+                                                client->check_align)) {
383d26
+        /*
383d26
+         * The block layer gracefully handles unaligned requests, but
383d26
+         * it's still worth tracing client non-compliance
383d26
+         */
383d26
+        trace_nbd_co_receive_align_compliance(nbd_cmd_lookup(request->type),
383d26
+                                              request->from,
383d26
+                                              request->len,
383d26
+                                              client->check_align);
383d26
+    }
383d26
     valid_flags = NBD_CMD_FLAG_FUA;
383d26
     if (request->type == NBD_CMD_READ && client->structured_reply) {
383d26
         valid_flags |= NBD_CMD_FLAG_DF;
383d26
diff --git a/nbd/trace-events b/nbd/trace-events
383d26
index 7f10ebd..bd42cc8 100644
383d26
--- a/nbd/trace-events
383d26
+++ b/nbd/trace-events
383d26
@@ -71,4 +71,5 @@ nbd_co_send_structured_error(uint64_t handle, int err, const char *errname, cons
383d26
 nbd_co_receive_request_decode_type(uint64_t handle, uint16_t type, const char *name) "Decoding type: handle = %" PRIu64 ", type = %" PRIu16 " (%s)"
383d26
 nbd_co_receive_request_payload_received(uint64_t handle, uint32_t len) "Payload received: handle = %" PRIu64 ", len = %" PRIu32
383d26
 nbd_co_receive_request_cmd_write(uint32_t len) "Reading %" PRIu32 " byte(s)"
383d26
+nbd_co_receive_align_compliance(const char *op, uint64_t from, uint32_t len, uint32_t align) "client sent non-compliant unaligned %s request: from=0x%" PRIx64 ", len=0x%" PRIx32 ", align=0x%" PRIx32
383d26
 nbd_trip(void) "Reading request"
383d26
-- 
383d26
1.8.3.1
383d26