qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Marcin Gibuła" <m.gibula@beyond.pl>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] qemu 2.0, deadlock in block-commit
Date: Sat, 24 May 2014 00:02:53 +0200	[thread overview]
Message-ID: <537FC58D.2020808@beyond.pl> (raw)
In-Reply-To: <537F4998.8030805@beyond.pl>

W dniu 2014-05-23 15:14, Marcin Gibuła pisze:
>>> bdrv_requests_pending(), called by bdrv_requests_pending_all(), is the
>>> function that determines for each of the disks in your VM if it still
>>> has requests in flight that need to be completed. This function must
>>> have returned true even though there is nothing to wait for.
>>>
>>> Can you check which of its conditions led to this behaviour, and for
>>> which disk it did? Either by setting a breakpoint there and
>>> singlestepping through the function the next time it is called (if the
>>> poll even has a timeout), or by inspecting the conditions manually in
>>> gdb.
>
> The condition that is true is:
>
> if (!QLIST_EMPTY(&bs->tracked_requests))
>
> and it's returned for intermediate qcow2 which is being commited.

My mistake, this condition is true not for intermediate file, but for an 
active one. Sorry for confusion.

-- 
mg

  parent reply	other threads:[~2014-05-23 22:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 20:49 [Qemu-devel] qemu 2.0, deadlock in block-commit Marcin Gibuła
2014-05-22 21:05 ` Marcin Gibuła
2014-05-23  8:19   ` Paolo Bonzini
2014-05-23  8:21     ` Marcin Gibuła
2014-05-23  9:25     ` Marcin Gibuła
2014-05-23 12:29       ` Kevin Wolf
2014-05-23 12:38         ` Marcin Gibuła
2014-05-23 13:14           ` Marcin Gibuła
2014-05-23 13:18             ` Marcin Gibuła
2014-05-23 22:02             ` Marcin Gibuła [this message]
2014-05-22 21:25 ` Eric Blake
2014-05-22 21:43   ` Marcin Gibuła
2014-05-23 12:58 ` Stefan Hajnoczi
2014-05-23 16:25   ` Marcin Gibuła

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=537FC58D.2020808@beyond.pl \
    --to=m.gibula@beyond.pl \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.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).