All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] Make qemu_peek_buffer loop until it gets it's data
Date: Fri, 21 Mar 2014 14:39:19 +0000	[thread overview]
Message-ID: <20140321143919.GA8476@work-vm> (raw)
In-Reply-To: <871txvit1p.fsf@elfo.mitica>

* Juan Quintela (quintela@redhat.com) wrote:
> "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com> wrote:
> > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >
> > Make qemu_peek_buffer repatedly call fill_buffer until it gets
> > all the data it requires, or until there is an error.
> >
> >   At the moment, qemu_peek_buffer will try one qemu_fill_buffer if there
> >   isn't enough data waiting, however the kernel is entitled to return
> >   just a few bytes, and still leave qemu_peek_buffer with less bytes
> >   than it needed.  I've seen this fail in a dev world, and I think it
> >   could theoretically fail in the peeking of the subsection headers in
> >   the current world.
> >
> > Ditto for qemu_peek_byte (which can only be affected due to it's
> > offset).
> >
> > Simplify qemu_get_buffer since it can now rely on qemu_peek_buffer to
> > loop.
> 
> I think this one is wrong, will explain there.
> 
> 
> > Use size_t rather than int for size parameters, (and result for
> > those functions that never return -errno).
> 
> Nice.
> 
> > -int qemu_get_buffer(QEMUFile *f, uint8_t *buf, int size)
> > +size_t qemu_get_buffer(QEMUFile *f, uint8_t *buf, size_t size)
> >  {
> > -    int pending = size;
> > -    int done = 0;
> > +    size_t res;
> >  
> > -    while (pending > 0) {
> > -        int res;
> > +    res = qemu_peek_buffer(f, buf, size, 0);
> >  
> > -        res = qemu_peek_buffer(f, buf, pending, 0);
> > -        if (res == 0) {
> > -            return done;
> > -        }
> > -        qemu_file_skip(f, res);
> > -        buf += res;
> > -        pending -= res;
> > -        done += res;
> > -    }
> > -    return done;
> > +    qemu_file_skip(f, res);
> > +
> > +    return res;
> 
> I think this is "theoretical" (a.k.a. no user of this functionality).
> As this was coded, we could receive buffers bigger than IOBUF_SIZE, with
> your change, we can't.  Just maintating the loop should fix this, right?

Ah, actually that is a good point (I've got a feeling one of my other
worlds relies on that); yes, I'll put the loop back and fix it all to be
size_t.

> > +    while (index >= f->buf_size) {
> > +        int received = qemu_fill_buffer(f);
> > +
> > +        if (received <= 0) {
> 
> here, I don't know really what to do.  We just need one character, so
> the 1st call to qemu_fill_buffer() gives it to us, or we are already on
> problems.  i.e. no need of the while() loop.

The problem is that peek_byte takes an offset, so while qemu_fill_buffer
will get us a byte, we actually need it to get us all the bytes upto the
offset, and that's not guaranteed from one call.

> On the other hand, having exactly the same code looks so nice.
> 
> At some point I was thinking about making qemu_peek_byte() to use
> qemu_peek_buffer(), but I think that we used qemu_peek_byte() more to
> justify the overhead.  I am talking from memory here.
> 
> 
> > diff --git a/vmstate.c b/vmstate.c
> > index d1f5eb0..b8e6e31 100644
> > --- a/vmstate.c
> > +++ b/vmstate.c
> > @@ -170,7 +170,7 @@ static int vmstate_subsection_load(QEMUFile *f, const VMStateDescription *vmsd,
> >          }
> >          size = qemu_peek_buffer(f, (uint8_t *)idstr, len, 2);
> >          if (size != len) {
> > -            return 0;
> > +            return -EIO;
> >          }
> >          idstr[size] = 0;
> 
> This was coded this way on purpose.  If we don't have a valid buffer
> after the subsection identifier, just let the code continue to see if it
> wasn't a subsection at all.  This colud be removed one tested that we
> don't allow subsections in the middle of a section, only in places where
> a section can appear.
> 
> In general, very nice patch, and fixes the problem.

Thanks, I'll rework and get a V2 up later.

Dave
> 
> Later, Juan.
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2014-03-21 14:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 12:58 [Qemu-devel] [PATCH 1/1] Make qemu_peek_buffer loop until it gets it's data Dr. David Alan Gilbert (git)
2014-03-21 13:24 ` Juan Quintela
2014-03-21 14:39   ` Dr. David Alan Gilbert [this message]
2014-03-21 16:05     ` Juan Quintela
2014-03-21 16:26       ` Dr. David Alan Gilbert
2014-03-21 17:55         ` Juan Quintela

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=20140321143919.GA8476@work-vm \
    --to=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.