qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/2] char: fix broken EAGAIN retry on OS-X due to errno clobbering
Date: Thu, 31 Mar 2016 15:37:48 +0100	[thread overview]
Message-ID: <20160331143748.GF12462@redhat.com> (raw)
In-Reply-To: <CAFEAcA9mQGCrxPXyyAik11+1fXL40Js_CUJdWo9OY+KFMdD8Yw@mail.gmail.com>

On Thu, Mar 31, 2016 at 03:35:44PM +0100, Peter Maydell wrote:
> On 31 March 2016 at 15:29, Daniel P. Berrange <berrange@redhat.com> wrote:
> > Some of the chardev I/O paths really want to write the
> > complete data buffer even though the channel is in
> > non-blocking mode. To achieve this they look for EAGAIN
> > and g_usleep() for 100ms. Unfortunately the code is set
> > to check errno == EAGAIN a second time, after the g_usleep()
> > call has completed. On OS-X at least, g_usleep clobbers
> > errno to ETIMEDOUT, causing the retry to be skipped.
> >
> > This failure to retry means the full data isn't written
> > to the chardev backend, which causes various failures
> > including making the tests/ahci-test qtest hang.
> >
> > Rather than playing games trying to reset errno just
> > simplify the code to use a goto to retry instead of a
> > a loop.
> >
> > Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> > ---
> >  qemu-char.c | 24 ++++++++++++------------
> >  1 file changed, 12 insertions(+), 12 deletions(-)
> >
> > diff --git a/qemu-char.c b/qemu-char.c
> > index 270819a..6e623c3 100644
> > --- a/qemu-char.c
> > +++ b/qemu-char.c
> > @@ -246,12 +246,12 @@ static int qemu_chr_fe_write_buffer(CharDriverState *s, const uint8_t *buf, int
> >
> >      qemu_mutex_lock(&s->chr_write_lock);
> >      while (*offset < len) {
> > -        do {
> > -            res = s->chr_write(s, buf + *offset, len - *offset);
> > -            if (res == -1 && errno == EAGAIN) {
> > -                g_usleep(100);
> > -            }
> > -        } while (res == -1 && errno == EAGAIN);
> > +    retry:
> > +        res = s->chr_write(s, buf + *offset, len - *offset);
> > +        if (res < 0 && errno == EAGAIN) {
> > +            g_usleep(100);
> > +            goto retry;
> > +        }
> >
> >          if (res <= 0) {
> >              break;
> > @@ -333,12 +333,12 @@ int qemu_chr_fe_read_all(CharDriverState *s, uint8_t *buf, int len)
> >      }
> >
> >      while (offset < len) {
> > -        do {
> > -            res = s->chr_sync_read(s, buf + offset, len - offset);
> > -            if (res == -1 && errno == EAGAIN) {
> > -                g_usleep(100);
> > -            }
> > -        } while (res == -1 && errno == EAGAIN);
> > +    retry:
> > +        res = s->chr_sync_read(s, buf + offset, len - offset);
> > +        if (res == -1 && errno == EAGAIN) {
> > +            g_usleep(100);
> > +            goto retry;
> > +        }
> >
> >          if (res == 0) {
> >              break;
> 
> qemu_chr_fe_write_log() also seems to have this broken retry pattern.

Oh yes, so it does. Will resend a v2.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2016-03-31 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31 14:29 [Qemu-devel] [PATCH 0/2] Fixing non-blocking operation of chardevs Daniel P. Berrange
2016-03-31 14:29 ` [Qemu-devel] [PATCH 1/2] char: fix broken EAGAIN retry on OS-X due to errno clobbering Daniel P. Berrange
2016-03-31 14:35   ` Peter Maydell
2016-03-31 14:37     ` Daniel P. Berrange [this message]
2016-03-31 14:29 ` [Qemu-devel] [PATCH 2/2] char: ensure all clients are in non-blocking mode Daniel P. Berrange

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=20160331143748.GF12462@redhat.com \
    --to=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.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).