From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>
Cc: Serge Hallyn <serge.hallyn@ubuntu.com>,
Michael Tokarev <mjt@tls.msk.ru>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [PATCH] accel/kvm/kvm-all: Fix wrong return code handling in dirty log code
Date: Fri, 29 Jan 2021 10:39:51 +0100 [thread overview]
Message-ID: <9583f48a-3103-2cde-ccfc-a6bd6517b29b@redhat.com> (raw)
In-Reply-To: <5531b70e-91df-2f38-df40-7346f5e496b5@redhat.com>
On 29/01/2021 10.28, Philippe Mathieu-Daudé wrote:
> On 1/29/21 9:43 AM, Thomas Huth wrote:
>> The kvm_vm_ioctl() wrapper already returns -errno if the ioctl itself
>> returned -1, so the callers of kvm_vm_ioctl() should not check for -1
>> but for a value < 0 instead.
>>
>> This problem has been fixed once already in commit b533f658a98325d0e4
>> but that commit missed that the ENOENT error code is not fatal for
>> this ioctl, so the commit has been reverted in commit 50212d6346f33d6e
>> since the problem occurred close to a pending release at that point
>> in time. The plan was to fix it properly after the release, but it
>> seems like this has been forgotten. So let's do it now finally instead.
>>
>> Resolves: https://bugs.launchpad.net/qemu/+bug/1294227
>
> Is this the "Close the oldest Launchpad bug" contest? =)
No, in that case I'd had tried to fix
https://bugs.launchpad.net/qemu/+bug/304636 instead ;-)
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Thanks!
Thomas
next prev parent reply other threads:[~2021-01-29 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 8:43 [PATCH] accel/kvm/kvm-all: Fix wrong return code handling in dirty log code Thomas Huth
2021-01-29 9:28 ` Philippe Mathieu-Daudé
2021-01-29 9:39 ` Thomas Huth [this message]
2021-01-29 9:38 ` Paolo Bonzini
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=9583f48a-3103-2cde-ccfc-a6bd6517b29b@redhat.com \
--to=thuth@redhat.com \
--cc=dgilbert@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=serge.hallyn@ubuntu.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 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).