From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qed: Fix consistency check on 32-bit hosts
Date: Tue, 26 Apr 2011 10:44:39 +0200 [thread overview]
Message-ID: <4DB685F7.7020603@redhat.com> (raw)
In-Reply-To: <1303666738-26558-1-git-send-email-stefanha@linux.vnet.ibm.com>
Am 24.04.2011 19:38, schrieb Stefan Hajnoczi:
> The qed_bytes_to_clusters() function is normally used with size_t
> lengths. Consistency check used it with file size length and therefore
> failed on 32-bit hosts when the image file is 4 GB or more.
>
> Make qed_bytes_to_clusters() explicitly 64-bit and update consistency
> check to keep 64-bit cluster counts.
>
> Reported-by: Michael Tokarev <mjt@tls.msk.ru>
> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Thanks, applied to the block branch.
Kevin
next prev parent reply other threads:[~2011-04-26 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 17:38 [Qemu-devel] [PATCH] qed: Fix consistency check on 32-bit hosts Stefan Hajnoczi
2011-04-26 8:44 ` Kevin Wolf [this message]
2011-04-26 9:48 ` Stefan Hajnoczi
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=4DB685F7.7020603@redhat.com \
--to=kwolf@redhat.com \
--cc=Qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).