From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: Eric Blake <eblake@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
Denis Lunev <den@virtuozzo.com>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] nbd/server: fix NBD_CMD_CACHE
Date: Thu, 4 Oct 2018 15:02:25 +0200 [thread overview]
Message-ID: <20181004130225.GE6009@localhost.localdomain> (raw)
In-Reply-To: <eb157eaa-b55d-3044-3c25-46a7d8e998f9@virtuozzo.com>
Am 03.10.2018 um 17:10 hat Vladimir Sementsov-Ogievskiy geschrieben:
> 03.10.2018 17:57, Eric Blake wrote:
> > On 10/3/18 9:47 AM, Vladimir Sementsov-Ogievskiy wrote:
> >> We should not go to structured-read branch on CACHE command, fix that.
> >>
> >> Bug intoroduced in bc37b06a5cde24 "nbd/server: introduce NBD_CMD_CACHE"
> >
> > s/intoroduced/introduced/
> >
> >> with the whole feature and affects 3.0.0 release.
> >
> > Ouch. It's because I don't have an NBD client that can issue the
> > command, so the server side got released without sufficient testing.
> > Is there some way we could enhance qemu-io as NBD client to issue such
> > a command?
>
> may be, just add qemu-io command, like x-debug-nbd-cmd, which will just
> send any nbd command? and prints all server replies? Then we'll be able
> to write any unit tests on nbd-server. It's not the first time the
> problem arise..
Shouldn't it be easy to write a simple NBD client in Python and then use
that for test cases? I don't see why this needs to be in qemu-io, and
testing illegal requests is certainly easier with a custom client.
Kevin
next prev parent reply other threads:[~2018-10-04 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 14:47 [Qemu-devel] [PATCH] nbd/server: fix NBD_CMD_CACHE Vladimir Sementsov-Ogievskiy
2018-10-03 14:57 ` Eric Blake
2018-10-03 15:10 ` Vladimir Sementsov-Ogievskiy
2018-10-04 13:02 ` Kevin Wolf [this message]
2018-10-04 14:29 ` [Qemu-devel] [Qemu-block] " 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=20181004130225.GE6009@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=den@virtuozzo.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).