From: Jeff Cody <jcody@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: kwolf@redhat.com, qemu-block@nongnu.org,
mitake.hitoshi@lab.ntt.co.jp, qemu-devel@nongnu.org,
v.tolstov@selfip.ru, pbonzini@redhat.com, namei.unix@gmail.com
Subject: Re: [Qemu-devel] [PATCH v3 1/1] block/sheepdog: fix argument passed to qemu_strtoul()
Date: Wed, 2 Mar 2016 11:36:09 -0500 [thread overview]
Message-ID: <20160302163609.GI26318@localhost.localdomain> (raw)
In-Reply-To: <56D7158B.5050107@redhat.com>
On Wed, Mar 02, 2016 at 05:32:11PM +0100, Max Reitz wrote:
> On 02.03.2016 17:24, Jeff Cody wrote:
> > The function qemu_strtoul() reads 'unsigned long' sized data,
> > which is larger than uint32_t on 64-bit machines.
> >
> > Even though the snap_id field in the header is 32-bits, we must
> > accomodate the full size in qemu_strtoul().
> >
> > This patch also adds more meaningful error handling to the
> > qemu_strtoul() call, and subsequent results.
> >
> > Reported-by: Paolo Bonzini <pbonzini@redhat.com>
> > Signed-off-by: Jeff Cody <jcody@redhat.com>
> > ---
> > block/sheepdog.c | 11 +++++++----
> > 1 file changed, 7 insertions(+), 4 deletions(-)
>
> Another problem with this function is that it doesn't always set errp on
> error. Actually, this patch introduces the first instance where it does.
>
> qemu-img will not print an error if errp is not set; it actually ignores
> bdrv_snapshot_delete_by_id_or_name()'s return value. So this is a real
> issue that should be fixed as well.
>
I'll (or perhaps one of the sheepdog maintainers?) will handle that in
subsequent patch(es).
next prev parent reply other threads:[~2016-03-02 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 16:24 [Qemu-devel] [PATCH v3 1/1] block/sheepdog: fix argument passed to qemu_strtoul() Jeff Cody
2016-03-02 16:28 ` Max Reitz
2016-03-02 16:30 ` Eric Blake
2016-03-02 16:36 ` Jeff Cody
2016-03-02 16:32 ` Max Reitz
2016-03-02 16:36 ` Jeff Cody [this message]
2016-03-03 4:07 ` Hitoshi Mitake
2016-03-03 4:06 ` Hitoshi Mitake
2016-03-10 2:35 ` Jeff Cody
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=20160302163609.GI26318@localhost.localdomain \
--to=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mitake.hitoshi@lab.ntt.co.jp \
--cc=mreitz@redhat.com \
--cc=namei.unix@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=v.tolstov@selfip.ru \
/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).