qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <1294227@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1294227] Re: migration wrong handling of KVM_GET_DIRTY_LOG ioctl
Date: Fri, 30 Apr 2021 08:54:36 -0000	[thread overview]
Message-ID: <161977287739.13825.5984271101510312596.launchpad@wampee.canonical.com> (raw)
In-Reply-To: 20140318172403.30474.3932.malonedeb@soybean.canonical.com

** Changed in: qemu
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1294227

Title:
  migration wrong handling of KVM_GET_DIRTY_LOG ioctl

Status in QEMU:
  Fix Released

Bug description:
  In the code below kvm_vm_ioctl(...) can return --errno != -1 from ioctl call,  but return only checks for -1. 
  Found during KVM-ARM migration which apperead to go through but was actually failing getting 
  memslot dirty bitmap.

  static int kvm_physical_sync_dirty_bitmap(....)
  {
   ....
   if(kvm_vm_ioctl(s, KVM_GET_DIRTY_LOG, &d) == -1) {
     - err out
   }
   ... continue
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1294227/+subscriptions


      parent reply	other threads:[~2021-04-30  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 17:24 [Qemu-devel] [Bug 1294227] [NEW] migration wrong handling of KVM_GET_DIRTY_LOG ioctl Mario Smarduch
2014-09-29 13:59 ` [Qemu-devel] [Bug 1294227] " Christoffer Dall
2014-09-29 14:08 ` Christoffer Dall
2020-11-04 22:46 ` John Snow
2021-01-29  8:54 ` Thomas Huth
2021-02-09 14:25 ` Thomas Huth
2021-04-30  8:54 ` Thomas Huth [this message]

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=161977287739.13825.5984271101510312596.launchpad@wampee.canonical.com \
    --to=1294227@bugs.launchpad.net \
    --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).