From: Kevin Wolf <kwolf@redhat.com>
To: Frediano Ziglio <freddy77@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qcow2: fix 028 iotest
Date: Fri, 23 Sep 2011 14:31:41 +0200 [thread overview]
Message-ID: <4E7C7C2D.5000102@redhat.com> (raw)
In-Reply-To: <1316777156-21477-1-git-send-email-freddy77@gmail.com>
Am 23.09.2011 13:25, schrieb Frediano Ziglio:
> This fix bound check bug accessing last cluster if image size is not
> cluster aligned caused by "Unlock during COW" patch.
>
> Signed-off-by: Frediano Ziglio <freddy77@gmail.com>
I'm considering a solution like this, but I'm not completely happy with
it. Maybe the more correct thing would be to restrict the request to the
allowed size in copy_sectors.
Anyway, if I decide that this is the way to go, I'll merge this fix into
my patch along with a notice in the commit log (better than two
independent commits in terms of bisectablity).
Kevin
prev parent reply other threads:[~2011-09-23 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 11:25 [Qemu-devel] [PATCH] qcow2: fix 028 iotest Frediano Ziglio
2011-09-23 12:31 ` Kevin Wolf [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=4E7C7C2D.5000102@redhat.com \
--to=kwolf@redhat.com \
--cc=freddy77@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.