From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@redhat.com>,
Alberto Garcia <berto@igalia.com>
Subject: Re: [Qemu-devel] [PATCH v2 9/9] iotests: Add test for COR across nodes
Date: Tue, 24 Apr 2018 18:50:37 +0200 [thread overview]
Message-ID: <20180424165037.GE4080@localhost.localdomain> (raw)
In-Reply-To: <20180421132929.21610-10-mreitz@redhat.com>
Am 21.04.2018 um 15:29 hat Max Reitz geschrieben:
> COR across nodes (that is, you have some filter node between the
> actually COR target and the node that performs the COR) cannot reliably
> work together with the permission system when there is no explicit COR
> node that can request the WRITE_UNCHANGED permission for its child.
> This is because COR (currently) sneaks its requests by the usual
> permission checks, so it can work without a WRITE* permission; but if
> there is a filter node in between, that will re-issue the request, which
> then passes through the usual check -- and if nobody has requested a
> WRITE_UNCHANGED permission, that check will fail.
>
> There is no real direct fix apart from hoping that there is someone who
> has requested that permission; in case of just the qemu-io HMP command
> (and no guest device), however, that is not the case. The real real fix
> is to implement the copy-on-read flag through an implicitly added COR
> node. Such a node can request the necessary permissions as shown in
> this test.
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> tests/qemu-iotests/216 | 117 +++++++++++++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/216.out | 28 +++++++++++
> tests/qemu-iotests/group | 1 +
> 3 files changed, 146 insertions(+)
> create mode 100755 tests/qemu-iotests/216
> create mode 100644 tests/qemu-iotests/216.out
>
> diff --git a/tests/qemu-iotests/216 b/tests/qemu-iotests/216
> new file mode 100755
> index 0000000000..b362cf93a8
> --- /dev/null
> +++ b/tests/qemu-iotests/216
> @@ -0,0 +1,117 @@
> +#!/usr/bin/env python
> +#
> +# Copy-on-read tests using a COR filter node
> +#
> +# Copyright (C) 2018 Red Hat, Inc.
> +#
> +# This program is free software; you can redistribute it and/or modify
> +# it under the terms of the GNU General Public License as published by
> +# the Free Software Foundation; either version 2 of the License, or
> +# (at your option) any later version.
> +#
> +# This program is distributed in the hope that it will be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> +# GNU General Public License for more details.
> +#
> +# You should have received a copy of the GNU General Public License
> +# along with this program. If not, see <http://www.gnu.org/licenses/>.
> +#
> +# Creator/Owner: Max Reitz <mreitz@redhat.com>
> +#
> +# Non-shared storage migration test using NBD server and drive-mirror
> +
> +import iotests
> +from iotests import log, qemu_img_pipe, qemu_io, filter_qemu_io
> +
> +# Need backing file support
> +iotests.verify_image_format(supported_fmts=['qcow2', 'qcow', 'qed', 'vmdk'])
> +iotests.verify_platform(['linux'])
> +
> +log('')
> +log('=== Copy-on-read across nodes ===')
> +log('')
> +
> +# The old copy-on-read mechanism without a filter node cannot request
> +# WRITE_UNCHANGED permissions for its child. Therefore it just tries
> +# to sneak its write by the usual permission system and holds its
> +# fingers crossed. However, that sneaking does not work so well when
> +# there is a filter node in the way: That will receive the write
> +# request and re-issue a new one to its child, which this time is a
> +# proper write request that will make the permission system cough --
> +# unless there is someone at the top (like a guest device) that has
> +# requested write permissions.
> +#
> +# A COR filter node, however, can request the proper permissions for
> +# its child and therefore is not hit by this issue.
> +
> +with iotests.FilePath('base.img') as base_img_path, \
> + iotests.FilePath('top.img') as top_img_path, \
> + iotests.VM() as vm:
> +
> + log('--- Setting up images ---')
> + log('')
> +
> + qemu_img_pipe('create', '-f', iotests.imgfmt, base_img_path, '64M')
> +
> + log(filter_qemu_io(qemu_io(base_img_path, '-c', 'write -P 1 0M 1M')))
> +
> + qemu_img_pipe('create', '-f', iotests.imgfmt, '-b', base_img_path,
> + top_img_path)
> +
> + log(filter_qemu_io(qemu_io(top_img_path, '-c', 'write -P 2 1M 1M')))
> +
> + log('')
> + log('--- Doing COR ---')
> + log('')
> +
> + # Compare with e.g. the following:
> + # vm.add_drive_raw('if=none,node-name=node0,copy-on-read=on,driver=raw,' \
> + # 'file.driver=%s,file.file.filename=%s' %
> + # (iotests.imgfmt, top_img_path))
> + # (Remove the blockdev-add instead.)
> + # ((Not tested here because it hits an assertion in the permission
> + # system.))
That's... kind of unfortunate.
This probably means that we can't continue with converting stuff like
throttling to filter nodes internally before this is fixed (i.e. copy on
read must be converted first). Let's hope it's the only one and we don't
end up with mutual dependencies...
Kevin
next prev parent reply other threads:[~2018-04-24 16:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 13:29 [Qemu-devel] [PATCH v2 0/9] block: Add COR filter driver Max Reitz
2018-04-21 13:29 ` [Qemu-devel] [PATCH v2 1/9] " Max Reitz
2018-04-24 15:08 ` Alberto Garcia
2018-04-25 11:18 ` Max Reitz
2018-04-25 11:35 ` Alberto Garcia
2018-04-21 13:29 ` [Qemu-devel] [PATCH v2 2/9] block: BLK_PERM_WRITE includes ..._UNCHANGED Max Reitz
2018-04-21 13:29 ` [Qemu-devel] [PATCH v2 3/9] block: Add BDRV_REQ_WRITE_UNCHANGED flag Max Reitz
2018-04-25 14:33 ` Eric Blake
2018-04-25 15:08 ` Max Reitz
2018-04-26 2:12 ` Eric Blake
2018-04-26 8:58 ` Kevin Wolf
2018-04-28 11:19 ` Max Reitz
2018-04-30 8:41 ` Kevin Wolf
2018-04-21 13:29 ` [Qemu-devel] [PATCH v2 4/9] block: Set BDRV_REQ_WRITE_UNCHANGED for COR writes Max Reitz
2018-04-21 13:29 ` [Qemu-devel] [PATCH v2 5/9] block/quorum: Support BDRV_REQ_WRITE_UNCHANGED Max Reitz
2018-04-21 13:29 ` [Qemu-devel] [PATCH v2 6/9] block: Support BDRV_REQ_WRITE_UNCHANGED in filters Max Reitz
2018-04-21 13:29 ` [Qemu-devel] [PATCH v2 7/9] iotests: Clean up wrap image in 197 Max Reitz
2018-04-21 13:29 ` [Qemu-devel] [PATCH v2 8/9] iotests: Copy 197 for COR filter driver Max Reitz
2018-04-24 15:17 ` Alberto Garcia
2018-04-21 13:29 ` [Qemu-devel] [PATCH v2 9/9] iotests: Add test for COR across nodes Max Reitz
2018-04-24 16:50 ` Kevin Wolf [this message]
2018-04-24 16:51 ` [Qemu-devel] [PATCH v2 0/9] block: Add COR filter driver Kevin Wolf
2018-04-25 12:18 ` Max Reitz
2018-04-25 14:36 ` Eric Blake
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=20180424165037.GE4080@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=berto@igalia.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).