From: Stefan Hajnoczi <stefanha@gmail.com>
To: Nick Thomas <nick@bytemark.co.uk>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
bluewindow@h3c.com
Subject: Re: [Qemu-devel] [PATCH 2/3] tests: add nbd-fault-injector.py utility
Date: Tue, 25 Feb 2014 17:25:43 +0100 [thread overview]
Message-ID: <20140225162543.GA4130@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <530C8247.8010000@bytemark.co.uk>
On Tue, Feb 25, 2014 at 11:45:11AM +0000, Nick Thomas wrote:
> On 25/02/14 10:09, Stefan Hajnoczi wrote:
> > + def send(self, buf, event):
> > + self.check(event, 'write', 'before')
> > + self.sock.sendall(buf)
> > + self.check(event, 'write', 'after')
> > +
> > + def recv(self, bufsize, event):
> > + self.check(event, 'read', 'before')
> > + data = recvall(self.sock, bufsize)
> > + self.check(event, 'read', 'after')
> > + return data
>
> There's a class of error I recently encountered in our out-of-tree proxy
> component that only shows up if a read or write is interrupted partway
> through. Perhaps you could have a "during" event here that happens after
> bufsize/2 bytes is written?
>
> I've not looked at qemu's block/nbd code recently, so I don't know if
> that exercises a particular failure path.
Yes, it can involve different code paths in the client. For example,
the client may receive fields in separate recv(2) syscalls so there may
be a unique path for each field.
I think the easiest approach is to turn the 'when' option into a byte
count. The connection will be terminated after the given number of
bytes.
Then 'before' becomes an alias for 0. 'after' becomes an alias for -1,
the magic value for the entire data length.
> > + def close(self):
> > + self.sock.close()
> > +
> > +def negotiate(conn):
> > + '''Negotiate export with client'''
> > + # Send negotiation part 1
> > + buf = neg1_struct.pack(NBD_PASSWD, NBD_OPTS_MAGIC, 0)
> > + conn.send(buf, event='neg1')
> > +
> > + # Receive export option
> > + buf = conn.recv(export_struct.size, event='export')
> > + export = export_tuple._make(export_struct.unpack(buf))
> > + assert export.magic == NBD_OPTS_MAGIC
> > + assert export.opt == NBD_OPT_EXPORT_NAME
> > + name = conn.recv(export.len, event='export-name')
> > +
> > + # Send negotiation part 2
> > + buf = neg2_struct.pack(8 * 1024 * 1024 * 1024, 0) # 8 GB capacity
> > + conn.send(buf, event='neg2')
>
> Is it worth exercising the old-style negotiation too?
Yes, probably a good idea.
next prev parent reply other threads:[~2014-02-25 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 10:09 [Qemu-devel] [PATCH 0/3] nbd: fix issues when connection breaks Stefan Hajnoczi
2014-02-25 10:09 ` [Qemu-devel] [PATCH 1/3] nbd: close socket if " Stefan Hajnoczi
2014-02-25 10:09 ` [Qemu-devel] [PATCH 2/3] tests: add nbd-fault-injector.py utility Stefan Hajnoczi
2014-02-25 11:45 ` Nick Thomas
2014-02-25 16:25 ` Stefan Hajnoczi [this message]
2014-02-25 10:09 ` [Qemu-devel] [PATCH 3/3] qemu-iotests: add 080 NBD client disconnect tests Stefan Hajnoczi
2014-02-25 10:16 ` Kevin Wolf
2014-02-25 11:16 ` Stefan Hajnoczi
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=20140225162543.GA4130@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=bluewindow@h3c.com \
--cc=kwolf@redhat.com \
--cc=nick@bytemark.co.uk \
--cc=pbonzini@redhat.com \
--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).