From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org,
kwolf@redhat.com, hreitz@redhat.com, vsementsov@virtuozzo.com,
jsnow@redhat.com, richard.henderson@linaro.org
Subject: [PULL v2 00/15] jobs: mirror: Handle errors after READY cancel
Date: Thu, 7 Oct 2021 17:39:00 +0200 [thread overview]
Message-ID: <20211007153904.445009-1-vsementsov@virtuozzo.com> (raw)
The following changes since commit 9618c5badaa8eed25259cf095ff880efb939fbe7:
Merge remote-tracking branch 'remotes/vivier/tags/trivial-branch-for-6.2-pull-request' into staging (2021-10-04 16:27:35 -0700)
are available in the Git repository at:
https://src.openvz.org/scm/~vsementsov/qemu.git tags/pull-jobs-2021-10-07-v2
for you to fetch changes up to 2451f72527d8760566a499b7513e17aaceb0f131:
iotests: Add mirror-ready-cancel-error test (2021-10-07 10:42:50 +0200)
----------------------------------------------------------------
mirror: Handle errors after READY cancel
v2: add small fix by Stefano, Hanna's series fixed
----------------------------------------------------------------
Hanna Reitz (13):
job: Context changes in job_completed_txn_abort()
mirror: Keep s->synced on error
mirror: Drop s->synced
job: Force-cancel jobs in a failed transaction
job: @force parameter for job_cancel_sync()
jobs: Give Job.force_cancel more meaning
job: Do not soft-cancel after a job is done
job: Add job_cancel_requested()
mirror: Use job_is_cancelled()
mirror: Check job_is_cancelled() earlier
mirror: Stop active mirroring after force-cancel
mirror: Do not clear .cancelled
iotests: Add mirror-ready-cancel-error test
Stefano Garzarella (2):
block/backup: avoid integer overflow of `max-workers`
block/aio_task: assert `max_busy_tasks` is greater than 0
include/qemu/job.h | 29 ++++++---
block/aio_task.c | 2 +
block/backup.c | 7 ++-
block/mirror.c | 56 +++++++++--------
block/replication.c | 4 +-
blockdev.c | 4 +-
job.c | 94 +++++++++++++++++++++++-----
tests/unit/test-blockjob.c | 2 +-
tests/qemu-iotests/109.out | 60 ++++++++----------
tests/qemu-iotests/tests/mirror-ready-cancel-error | 143 +++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/tests/mirror-ready-cancel-error.out | 5 ++
tests/qemu-iotests/tests/qsd-jobs.out | 2 +-
12 files changed, 316 insertions(+), 92 deletions(-)
create mode 100755 tests/qemu-iotests/tests/mirror-ready-cancel-error
create mode 100644 tests/qemu-iotests/tests/mirror-ready-cancel-error.out
--
2.31.1
next reply other threads:[~2021-10-07 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 15:39 Vladimir Sementsov-Ogievskiy [this message]
2021-10-07 15:39 ` [PULL v2 01/15] block/backup: avoid integer overflow of `max-workers` Vladimir Sementsov-Ogievskiy
2021-10-07 15:39 ` [PULL v2 02/15] block/aio_task: assert `max_busy_tasks` is greater than 0 Vladimir Sementsov-Ogievskiy
2021-10-07 15:39 ` [PULL v2 09/15] job: Do not soft-cancel after a job is done Vladimir Sementsov-Ogievskiy
2021-10-07 15:39 ` [PULL v2 10/15] job: Add job_cancel_requested() Vladimir Sementsov-Ogievskiy
2021-10-07 19:06 ` [PULL v2 00/15] jobs: mirror: Handle errors after READY cancel Richard Henderson
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=20211007153904.445009-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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).