From: Eric Blake <eblake@redhat.com>
To: Gary Hook <gary.hook@nimboxx.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/1] block migration: fix return value mismatch
Date: Wed, 12 Nov 2014 13:27:11 -0700 [thread overview]
Message-ID: <5463C29F.90700@redhat.com> (raw)
In-Reply-To: <D0890790.3A5A%gary.hook@nimboxx.com>
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
On 11/12/2014 11:48 AM, Gary Hook wrote:
> The function uses a ternary return value (<, >, == 0) defined as an int. The code in in this function uses int64_t types to collect ftell() return values and use their difference as the return value. Unfortunately, narrowing of integer types results in the disposal of the left-most bits that won't fit in the target type. Here, for values larger than 2GB, the resulting value will be randomly negative or positive, based on total number of blocks. The patch ensures that only +1, -1, or 0 are returned to properly report status.
>
Please wrap commit messages at around 70 characters ('git log' likes to
indent, and people still like to use 80-column windows to read 'git log').
>
>
>
> diff -u -r a/block-migration.c b/block-migration.c
>
Your patch is missing a 'Signed-off-by' line, which is essential to
getting it applied. It is also missing the typical '---' separator
between commit message and patch body.
> --- a/block-migration.c 2014-04-17 08:30:59.000000000 -0500
>
> +++ b/block-migration.c 2014-11-10 12:39:10.727431187 -0600
>
> @@ -628,6 +628,7 @@
Your patch is mal-formed, with too many blank lines inserted by your
mailer. We generally request that you use 'git send-email' rather than
manually pasting your patch into an email, since git is more likely to
send a correctly-formed message.
Also, it appears that you sent a 0/1 cover letter, but forgot to put
this message as In-Reply-To that message. For a single patch, no cover
letter is necessary; but for a patch series, it is important to properly
thread your emails.
More details on proper patch submission can be found here:
http://wiki.qemu.org/Contribute/SubmitAPatch
At any rate, the patch looks reasonable, so please resend it as v2 with
your Signed-off-by.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
next prev parent reply other threads:[~2014-11-12 20:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 18:48 [Qemu-devel] [PATCH 1/1] block migration: fix return value mismatch Gary Hook
2014-11-12 20:27 ` Eric Blake [this message]
2014-11-13 7:57 ` Markus Armbruster
2014-11-13 11:20 ` Stefan Hajnoczi
2014-11-13 12:46 ` Markus Armbruster
-- strict thread matches above, loose matches on Subject: below --
2014-11-13 16:43 Gary Hook
2014-11-13 16:44 Gary Hook
2014-11-13 17:03 ` Eric Blake
2014-11-13 17:32 ` Gary Hook
2014-11-13 18:55 ` Stefan Hajnoczi
2014-11-13 21:12 ` Gary R Hook
2014-11-21 18:08 Gary R Hook
2014-11-24 9:10 ` Dr. David Alan Gilbert
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=5463C29F.90700@redhat.com \
--to=eblake@redhat.com \
--cc=gary.hook@nimboxx.com \
--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).