From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, Alexander Graf <agraf@suse.de>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-stable] [PULL 1/1] KVM: Use return value for error print
Date: Thu, 27 Feb 2014 09:52:31 -0600 [thread overview]
Message-ID: <20140227155231.28890.28800@loki> (raw)
In-Reply-To: <1393325096-8338-2-git-send-email-pbonzini@redhat.com>
Quoting Paolo Bonzini (2014-02-25 04:44:56)
> From: Alexander Graf <agraf@suse.de>
>
> Commit 94ccff13 introduced a more verbose failure message and retry
> operations on KVM VM creation. However, it ended up using a variable
> for its failure message that hasn't been initialized yet.
>
> Fix it to use the value it meant to set.
>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Alexander Graf <agraf@suse.de>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Ping: last call for 1.7.1 (freeze today)
> ---
> kvm-all.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/kvm-all.c b/kvm-all.c
> index f742f8d..979a8d9 100644
> --- a/kvm-all.c
> +++ b/kvm-all.c
> @@ -1427,7 +1427,7 @@ int kvm_init(void)
> } while (ret == -EINTR);
>
> if (ret < 0) {
> - fprintf(stderr, "ioctl(KVM_CREATE_VM) failed: %d %s\n", -s->vmfd,
> + fprintf(stderr, "ioctl(KVM_CREATE_VM) failed: %d %s\n", -ret,
> strerror(-ret));
>
> #ifdef TARGET_S390X
> --
> 1.7.1
next prev parent reply other threads:[~2014-02-27 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 10:44 [Qemu-devel] [PULL 0/1] Lonely uq/master patch for 2014-02-24 Paolo Bonzini
2014-02-25 10:44 ` [Qemu-devel] [PULL 1/1] KVM: Use return value for error print Paolo Bonzini
2014-02-27 15:52 ` Michael Roth [this message]
2014-02-27 16:11 ` [Qemu-devel] [PULL 0/1] Lonely uq/master patch for 2014-02-24 Peter Maydell
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=20140227155231.28890.28800@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).