From: Alberto Garcia <berto@igalia.com>
To: qemu-devel@nongnu.org
Cc: Alberto Garcia <berto@igalia.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>,
Kevin Wolf <kwolf@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/2] commit: Make base read-only if there is an early failure
Date: Mon, 29 Apr 2019 15:51:07 +0200 [thread overview]
Message-ID: <cover.1556540297.git.berto@igalia.com> (raw)
Hi,
Here's v3 of this series, the only changes are the corrections in the
iotest suggested by Max.
Regards,
Berto
v3:
- Patch 2: Use $() instead of backquotes, remove 'here' variable and
don't use 'sleep' when waiting for block-commit to finish [Max]
v2: https://lists.gnu.org/archive/html/qemu-block/2019-04/msg00334.html
- Patch 2: Added test case
v1: https://lists.gnu.org/archive/html/qemu-block/2019-04/msg00281.html
Output of backport-diff against v2:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
Alberto Garcia (2):
commit: Make base read-only if there is an early failure
iotests: Check that images are in read-only mode after block-commit
block/commit.c | 3 ++
tests/qemu-iotests/249 | 115 +++++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/249.out | 35 ++++++++++++++
tests/qemu-iotests/group | 1 +
4 files changed, 154 insertions(+)
create mode 100755 tests/qemu-iotests/249
create mode 100644 tests/qemu-iotests/249.out
--
2.11.0
WARNING: multiple messages have this Message-ID (diff)
From: Alberto Garcia <berto@igalia.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Alberto Garcia <berto@igalia.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/2] commit: Make base read-only if there is an early failure
Date: Mon, 29 Apr 2019 15:51:07 +0200 [thread overview]
Message-ID: <cover.1556540297.git.berto@igalia.com> (raw)
Message-ID: <20190429135107.XtSg7r6g5JpzotLePcNSKV3hM19DdGe8Q44Qpx8TZVw@z> (raw)
Hi,
Here's v3 of this series, the only changes are the corrections in the
iotest suggested by Max.
Regards,
Berto
v3:
- Patch 2: Use $() instead of backquotes, remove 'here' variable and
don't use 'sleep' when waiting for block-commit to finish [Max]
v2: https://lists.gnu.org/archive/html/qemu-block/2019-04/msg00334.html
- Patch 2: Added test case
v1: https://lists.gnu.org/archive/html/qemu-block/2019-04/msg00281.html
Output of backport-diff against v2:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
Alberto Garcia (2):
commit: Make base read-only if there is an early failure
iotests: Check that images are in read-only mode after block-commit
block/commit.c | 3 ++
tests/qemu-iotests/249 | 115 +++++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/249.out | 35 ++++++++++++++
tests/qemu-iotests/group | 1 +
4 files changed, 154 insertions(+)
create mode 100755 tests/qemu-iotests/249
create mode 100644 tests/qemu-iotests/249.out
--
2.11.0
next reply other threads:[~2019-04-29 13:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 13:51 Alberto Garcia [this message]
2019-04-29 13:51 ` [Qemu-devel] [PATCH v3 0/2] commit: Make base read-only if there is an early failure Alberto Garcia
2019-04-29 13:51 ` [Qemu-devel] [PATCH v3 1/2] " Alberto Garcia
2019-04-29 13:51 ` Alberto Garcia
2019-04-29 13:51 ` [Qemu-devel] [PATCH v3 2/2] iotests: Check that images are in read-only mode after block-commit Alberto Garcia
2019-04-29 13:51 ` Alberto Garcia
2019-04-30 2:42 ` [Qemu-devel] [PATCH v3 0/2] commit: Make base read-only if there is an early failure no-reply
2019-04-30 2:42 ` no-reply
2019-04-30 7:02 ` no-reply
2019-04-30 7:02 ` no-reply
2019-04-30 11:20 ` Kevin Wolf
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=cover.1556540297.git.berto@igalia.com \
--to=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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.