kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: Endless loop in qcow2_alloc_cluster_offset
Date: Mon, 07 Dec 2009 17:26:00 +0100	[thread overview]
Message-ID: <4B1D2C98.6060502@redhat.com> (raw)
In-Reply-To: <4B1D28C9.70201@siemens.com>

Am 07.12.2009 17:09, schrieb Jan Kiszka:
> Kevin Wolf wrote:
>> In qcow_aio_write_cb there isn't much happening between these calls. The
>> only thing that could somehow become dangerous is the
>> qcow_aio_write_cb(req, 0); for queued requests in run_dependent_requests.
> 
> If m->nb_clusters is not, the entry won't be removed from the list. And
> of something corrupted nb_clusters so that it became 0 although it's
> still enqueued, we would see the deadly loop I faced, right?
> Unfortunately, any arbitrary memory corruption that generates such zeros
> can cause this...

Right, this looks like another way to get into that endless loop. I
don't think it's very likely the cause, but who knows.

Kevin

  reply	other threads:[~2009-12-07 16:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19 12:19 Endless loop in qcow2_alloc_cluster_offset Jan Kiszka
2009-11-19 14:49 ` Kevin Wolf
2009-11-19 14:58   ` Jan Kiszka
2009-12-07 14:16     ` Jan Kiszka
2009-12-07 14:50       ` Jan Kiszka
2009-12-07 15:03         ` Kevin Wolf
2009-12-07 15:25           ` Jan Kiszka
2009-12-07 15:04         ` Avi Kivity
2009-12-07 15:00       ` Kevin Wolf
2009-12-07 16:09         ` Jan Kiszka
2009-12-07 16:26           ` Kevin Wolf [this message]
2009-12-08 14:51         ` [Qemu-devel] " Kevin Wolf
2010-05-07  1:19 ` Marcelo Tosatti
2010-05-07  7:37   ` Kevin Wolf
2010-05-07 15:16     ` Marcelo Tosatti

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=4B1D2C98.6060502@redhat.com \
    --to=kwolf@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --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).