All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, pl@kamp.de,
	pbonzini@redhat.com, ronniesahlberg@gmail.com,
	stefanha@redhat.com, mreitz@redhat.com, kwolf@redhat.com,
	jcody@redhat.com, jsnow@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH v3 0/4] fix image fleecing
Date: Fri, 6 Jul 2018 16:41:50 +0300	[thread overview]
Message-ID: <7747e176-6d75-c640-4f48-0482b8c7c401@virtuozzo.com> (raw)
In-Reply-To: <20180706071754.GB9946@lemon.usersys.redhat.com>

06.07.2018 10:17, Fam Zheng wrote:
> On Thu, 07/05 10:46, Vladimir Sementsov-Ogievskiy wrote:
>> Hi all.
>>
>> This fixes image fleecing scheme for 3.0, details are in 04 patch.
> Looks like this breaks 'test-replication':
>
> http://patchew.org/QEMU/20180705074638.770905-1-vsementsov@virtuozzo.com/
>
> test-replication: /stor/work/qemu/block/io.c:725: wait_serialising_requests: Assertion `qemu_coroutine_self() != req->co' failed.
> GTester: last random seed: R02Se49967625f19c5be9918a2503fb2fff5
> test-replication: /stor/work/qemu/block/io.c:725: wait_serialising_requests: Assertion `qemu_coroutine_self() != req->co' failed.
>    GTESTER tests/test-qht-par
> GTester: last random seed: R02S8fad2bb2daddc51eb51623bb7c86cb67
> test-replication: /stor/work/qemu/block/io.c:725: wait_serialising_requests: Assertion `qemu_coroutine_self() != req->co' failed.
> GTester: last random seed: R02S024718e9b1e2b1facafe254c43e1430b
>
> Fam

interesting.

in gdb I see, that both requests are identical (i.e. their 
BdrvTrackedRequeststructs, except list filed)writes (self and req)...

and it's actually the same request, duplicated in the ist, first it is 
created in bdrv_co_copy_range_internal,

and than again,
#0  tracked_request_begin (req=0x7fffe8f9e7d0, bs=0x555555a43040, 
offset=33554432, bytes=33554432, type=
     BDRV_TRACKED_WRITE) at block/io.c:598
#1  0x00005555555f76bc in bdrv_co_copy_range_internal 
(src=0x55555597ef80, src_offset=33882112,
     dst=0x5555559f1d30, dst_offset=33554432, bytes=33554432, 
read_flags=BDRV_REQ_NO_SERIALISING,
     write_flags=BDRV_REQ_SERIALISING, recurse_src=true) at block/io.c:2949
#2  0x00005555555f78e9 in bdrv_co_copy_range_from (src=0x55555597ef80, 
src_offset=33882112,
     dst=0x5555559f1d30, dst_offset=33554432, bytes=33554432, 
read_flags=BDRV_REQ_NO_SERIALISING,
     write_flags=BDRV_REQ_SERIALISING) at block/io.c:2995
#3  0x00005555555ae931 in qcow2_co_copy_range_from (bs=0x555555977ff0, 
src=0x5555559f14d0,
     src_offset=33554432, dst=0x5555559f1d30, dst_offset=33554432, 
bytes=33554432,
     read_flags=BDRV_REQ_NO_SERIALISING, 
write_flags=BDRV_REQ_SERIALISING) at block/qcow2.c:3311
#4  0x00005555555f77cf in bdrv_co_copy_range_internal 
(src=0x5555559f14d0, src_offset=33554432,
     dst=0x5555559f1d30, dst_offset=33554432, bytes=33554432, 
read_flags=BDRV_REQ_NO_SERIALISING,
     write_flags=BDRV_REQ_SERIALISING, recurse_src=true) at block/io.c:2966


so, it's actually bug in copy_range architecture.

-- 
Best regards,
Vladimir

  reply	other threads:[~2018-07-06 13:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05  7:46 [Qemu-devel] [PATCH v3 0/4] fix image fleecing Vladimir Sementsov-Ogievskiy
2018-07-05  7:46 ` [Qemu-devel] [PATCH v3 1/4] block: disallow BDRV_REQ_NO_SERIALISING for write Vladimir Sementsov-Ogievskiy
2018-07-06 21:32   ` Eric Blake
2018-07-06 21:46     ` Eric Blake
2018-07-09 16:08       ` Vladimir Sementsov-Ogievskiy
2018-07-09 15:56     ` Vladimir Sementsov-Ogievskiy
2018-07-05  7:46 ` [Qemu-devel] [PATCH v3 2/4] block: split flags in copy_range Vladimir Sementsov-Ogievskiy
2018-07-05  7:46 ` [Qemu-devel] [PATCH v3 3/4] block: add BDRV_REQ_SERIALISING flag Vladimir Sementsov-Ogievskiy
2018-07-06 21:52   ` Eric Blake
2018-07-05  7:46 ` [Qemu-devel] [PATCH v3 4/4] block/backup: fix fleecing scheme: use serialized writes Vladimir Sementsov-Ogievskiy
2018-07-06  7:17 ` [Qemu-devel] [PATCH v3 0/4] fix image fleecing Fam Zheng
2018-07-06 13:41   ` Vladimir Sementsov-Ogievskiy [this message]
2018-07-06 14:34     ` Vladimir Sementsov-Ogievskiy

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=7747e176-6d75-c640-4f48-0482b8c7c401@virtuozzo.com \
    --to=vsementsov@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=pl@kamp.de \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=ronniesahlberg@gmail.com \
    --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 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.