From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 06/26] qcow2: Use 64 bits for refcount values
Date: Tue, 03 Feb 2015 14:48:35 -0500 [thread overview]
Message-ID: <54D12613.8040606@redhat.com> (raw)
In-Reply-To: <20150203192632.GH4488@noname.redhat.com>
On 2015-02-03 at 14:26, Kevin Wolf wrote:
> Am 15.12.2014 um 13:50 hat Max Reitz geschrieben:
>> Refcounts may have a width of up to 64 bits, so qemu should use the same
>> width to represent refcount values internally.
>>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>> block/qcow2-cluster.c | 2 +-
>> block/qcow2-refcount.c | 46 ++++++++++++++++++++++------------------------
>> block/qcow2.h | 4 ++--
>> 3 files changed, 25 insertions(+), 27 deletions(-)
>> @@ -897,11 +895,10 @@ int qcow2_update_snapshot_refcount(BlockDriverState *bs,
>> int64_t l1_table_offset, int l1_size, int addend)
>> {
> Your leaving addend an int here...
>
>> BDRVQcowState *s = bs->opaque;
>> - uint64_t *l1_table, *l2_table, l2_offset, offset, l1_size2;
>> + uint64_t *l1_table, *l2_table, l2_offset, offset, l1_size2, refcount;
>> bool l1_allocated = false;
>> int64_t old_offset, old_l2_offset;
>> int i, j, l1_modified = 0, nb_csectors;
>> - uint16_t refcount;
>> int ret;
>>
>> l2_table = NULL;
>> @@ -968,7 +965,7 @@ int qcow2_update_snapshot_refcount(BlockDriverState *bs,
>> if (addend != 0) {
>> ret = update_refcount(bs,
>> (offset & s->cluster_offset_mask) & ~511,
>> - nb_csectors * 512, abs(addend), addend < 0,
>> + nb_csectors * 512, imaxabs(addend), addend < 0,
>> QCOW2_DISCARD_SNAPSHOT);
>> if (ret < 0) {
>> goto fail;
>> @@ -999,7 +996,7 @@ int qcow2_update_snapshot_refcount(BlockDriverState *bs,
>> }
>> if (addend != 0) {
>> ret = qcow2_update_cluster_refcount(bs,
>> - cluster_index, abs(addend), addend < 0,
>> + cluster_index, imaxabs(addend), addend < 0,
>> QCOW2_DISCARD_SNAPSHOT);
>> if (ret < 0) {
>> goto fail;
>> @@ -1042,7 +1039,7 @@ int qcow2_update_snapshot_refcount(BlockDriverState *bs,
>> if (addend != 0) {
>> ret = qcow2_update_cluster_refcount(bs, l2_offset >>
>> s->cluster_bits,
>> - abs(addend), addend < 0,
>> + imaxabs(addend), addend < 0,
>> QCOW2_DISCARD_SNAPSHOT);
>> if (ret < 0) {
>> goto fail;
> ...but still replace abs() by imaxabs(). Did you intend to convert
> addend or why this change?
Mechanical replacement of every abs(addend) most likely.
Considering that qcow2_update_snapshot_refcount() is only called with
@addend \in { -1, 0, 1 }, it doesn't seem to make any technical sense to
convert @addend to something else than an int; and thus it doesn't make
any sense to use imaxabs() instead of abs() (although it doesn't hurt,
it just looks bad). Also, if I were to convert
qcow2_update_snapshot_refcount() to the "full 64 bit difference
interface", I'd need an additional argument for the sign of the addend.
Therefore, I'll drop the imaxabs() hunks for
qcow2_update_snapshot_refcount(), if you're fine with that.
>> @@ -1658,7 +1655,7 @@ static void compare_refcounts(BlockDriverState *bs, BdrvCheckResult *res,
>> {
>> BDRVQcowState *s = bs->opaque;
>> int64_t i;
>> - uint16_t refcount1, refcount2;
>> + uint64_t refcount1, refcount2;
>> int ret;
>>
>> for (i = 0, *highest_cluster = 0; i < nb_clusters; i++) {
>> @@ -1687,7 +1684,8 @@ static void compare_refcounts(BlockDriverState *bs, BdrvCheckResult *res,
>> num_fixed = &res->corruptions_fixed;
>> }
>>
>> - fprintf(stderr, "%s cluster %" PRId64 " refcount=%d reference=%d\n",
>> + fprintf(stderr, "%s cluster %" PRId64 " refcount=%" PRIu64
>> + " reference=%" PRIu64 "\n",
>> num_fixed != NULL ? "Repairing" :
>> refcount1 < refcount2 ? "ERROR" :
>> "Leaked",
>> @@ -1695,7 +1693,7 @@ static void compare_refcounts(BlockDriverState *bs, BdrvCheckResult *res,
>>
>> if (num_fixed) {
>> ret = update_refcount(bs, i << s->cluster_bits, 1,
>> - abs(refcount2 - refcount1),
>> + imaxabs(refcount2 - refcount1),
>> refcount1 > refcount2,
> Hope I got that right. Here's my analysis:
>
> Before: refcount{1,2} were both uint16_t. Promoted to int for the
> subtraction. Therefore a negative result could occur. abs() takes the
> absolute value and the sign is passed separately.
>
> After: refcount{1,2} are both uint64_t. No integer promotion happens, we
> perform an unsigned subtraction. The separate passed sign is okay. For
> the absolute value, there are two cases:
>
> 1. refcount2 >= refcount1: No overflow occurs, everything fine.
>
> 2. refcount2 < refcount1: (refcount2 - refcount1) wraps around, but is
> still an uint64_t. imaxabs() takes an intmax_t, which is signed. The
> conversion is implementation defined, but let's assume the obvious
> one. imaxabs() has two cases again:
>
> diff := refcount2 - refcount1 + UINT64_MAX
Actually it's + UINT64_MAX + 1, but it doesn't matter for the point
you're making.
> a. diff > INTMAX_MAX:
> We get diff converted back to signed, which undoes the wraparound.
> The absolute value of the signed difference is:
>
> -(refcount2 - refcount1) = refcount1 - refcount2
>
> This is what we wanted. Good.
>
> b. diff <= INTMAX_MAX:
> diff is again converted back to signed, however its value is
> unchanged because diff can be represented by intmax_t. This is a
> positive value, so taking the absolute value changes nothing.
>
> This is _not_ refcount1 - refcount2!
You're completely right. Actually, I won absolutely nothing by
separating the sign if using imaxabs() because the latter will only
return values in 0 .. 2^63 - 1, which makes it (using imaxabs()) a very
bad idea in the first place.
> I suggest using a function that calculates the absolute value of the
> difference of two unsigned values the naive way with an if statement.
> Gets us rid of the implementation defined conversion, too.
Indeed, will do. Thanks!
Max
>> QCOW2_DISCARD_ALWAYS);
>> if (ret >= 0) {
> Kevin
next prev parent reply other threads:[~2015-02-03 19:48 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 12:50 [Qemu-devel] [PATCH v5 00/26] qcow2: Support refcount orders != 4 Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 01/26] qcow2: Add two new fields to BDRVQcowState Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 02/26] qcow2: Add refcount_bits to format-specific info Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 03/26] qcow2: Do not return new value after refcount update Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 04/26] qcow2: Only return status from qcow2_get_refcount Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 05/26] qcow2: Use unsigned addend for update_refcount() Max Reitz
2015-01-22 15:33 ` Eric Blake
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 06/26] qcow2: Use 64 bits for refcount values Max Reitz
2015-01-22 15:35 ` Eric Blake
2015-02-03 19:26 ` Kevin Wolf
2015-02-03 19:48 ` Max Reitz [this message]
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 07/26] qcow2: Respect error in qcow2_alloc_bytes() Max Reitz
2015-02-04 11:40 ` Kevin Wolf
2015-02-04 15:04 ` Max Reitz
2015-02-04 15:12 ` Kevin Wolf
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 08/26] qcow2: Refcount overflow and qcow2_alloc_bytes() Max Reitz
2015-02-04 11:55 ` Kevin Wolf
2015-02-04 15:33 ` Max Reitz
2015-02-04 16:10 ` Kevin Wolf
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 09/26] qcow2: Helper for refcount array reallocation Max Reitz
2015-02-04 13:21 ` Kevin Wolf
2015-02-04 15:57 ` Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 10/26] qcow2: Helper function for refcount modification Max Reitz
2015-02-04 16:06 ` Kevin Wolf
2015-02-04 17:12 ` Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 11/26] qcow2: More helpers " Max Reitz
2015-02-04 13:53 ` Kevin Wolf
2015-02-04 15:59 ` Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 12/26] qcow2: Open images with refcount order != 4 Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 13/26] qcow2: refcount_order parameter for qcow2_create2 Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 14/26] qcow2: Use symbolic macros in qcow2_amend_options Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 15/26] iotests: Prepare for refcount_bits option Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 16/26] qcow2: Allow creation with refcount order != 4 Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 17/26] progress: Allow regressing progress Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 18/26] block: Add opaque value to the amend CB Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 19/26] qcow2: Use error_report() in qcow2_amend_options() Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 20/26] qcow2: Use abort() instead of assert(false) Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 21/26] qcow2: Split upgrade/downgrade paths for amend Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 22/26] qcow2: Use intermediate helper CB " Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 23/26] qcow2: Add function for refcount order amendment Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 24/26] qcow2: Invoke refcount order amendment function Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 25/26] qcow2: Point to amend function in check Max Reitz
2014-12-15 12:50 ` [Qemu-devel] [PATCH v5 26/26] iotests: Add test for different refcount widths Max Reitz
2015-01-20 22:48 ` [Qemu-devel] [PATCH v5 00/26] qcow2: Support refcount orders != 4 Max Reitz
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=54D12613.8040606@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).