All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Jeff Cody <jcody@redhat.com>,
	qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
	vsementsov@parallels.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v7 09/14] block: Add block job transactions
Date: Thu, 24 Sep 2015 16:29:16 +0800	[thread overview]
Message-ID: <20150924082902.GA24855@localhost.nay.redhat.com> (raw)
In-Reply-To: <5601A767.5060109@redhat.com>

On Tue, 09/22 15:09, John Snow wrote:
> 
> 
> On 09/21/2015 10:46 PM, Fam Zheng wrote:
> > Sometimes block jobs must execute as a transaction group.  Finishing
> > jobs wait until all other jobs are ready to complete successfully.
> > Failure or cancellation of one job cancels the other jobs in the group.
> > 
> > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> > [Rewrite the implementation which is now contained in block_job_completed.
> > --Fam]
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > Reviewed-by: Max Reitz <mreitz@redhat.com>
> > ---
> >  blockjob.c               | 135 ++++++++++++++++++++++++++++++++++++++++++++++-
> >  include/block/block.h    |   1 +
> >  include/block/blockjob.h |  38 +++++++++++++
> >  3 files changed, 172 insertions(+), 2 deletions(-)
> > 
> > diff --git a/blockjob.c b/blockjob.c
> > index 36c18e0..91e8d3c 100644
> > --- a/blockjob.c
> > +++ b/blockjob.c
> > @@ -36,6 +36,19 @@
> >  #include "qemu/timer.h"
> >  #include "qapi-event.h"
> >  
> > +/* Transactional group of block jobs */
> > +struct BlockJobTxn {
> > +
> > +    /* Is this txn being cancelled? */
> > +    bool aborting;
> > +
> > +    /* List of jobs */
> > +    QLIST_HEAD(, BlockJob) jobs;
> > +
> > +    /* Reference count */
> > +    int refcnt;
> > +};
> > +
> >  void *block_job_create(const BlockJobDriver *driver, BlockDriverState *bs,
> >                         int64_t speed, BlockCompletionFunc *cb,
> >                         void *opaque, Error **errp)
> > @@ -90,6 +103,86 @@ void block_job_unref(BlockJob *job)
> >      }
> >  }
> >  
> > +static void block_job_completed_single(BlockJob *job)
> > +{
> > +    if (!job->ret) {
> > +        if (job->driver->commit) {
> > +            job->driver->commit(job);
> > +        }
> > +    } else {
> > +        if (job->driver->abort) {
> > +            job->driver->abort(job);
> > +        }
> > +    }
> > +    job->cb(job->opaque, job->ret);
> > +    if (job->txn) {
> > +        block_job_txn_unref(job->txn);
> > +    }
> > +    block_job_unref(job);
> > +}
> > +
> > +static void block_job_completed_txn_abort(BlockJob *job)
> > +{
> > +    AioContext *ctx;
> > +    BlockJobTxn *txn = job->txn;
> > +    BlockJob *other_job, *next;
> > +
> > +    if (txn->aborting) {
> > +        /*
> > +         * We are cancelled by another job, which will handle everything.
> > +         */
> > +        return;
> > +    }
> > +    txn->aborting = true;
> > +    /* We are the first failed job. Cancel other jobs. */
> > +    QLIST_FOREACH(other_job, &txn->jobs, txn_list) {
> > +        ctx = bdrv_get_aio_context(other_job->bs);
> > +        aio_context_acquire(ctx);
> > +    }
> > +    QLIST_FOREACH(other_job, &txn->jobs, txn_list) {
> > +        if (other_job == job || other_job->completed) {
> > +            /* Other jobs are "effectively" cancelled by us, set the status for
> > +             * them; this job, however, may or may not be cancelled, depending
> > +             * on the caller, so leave it. */
> > +            if (other_job != job) {
> > +                other_job->cancelled = true;
> > +            }
> > +            continue;
> > +        }
> > +        block_job_cancel_sync(other_job);
> > +        assert(other_job->completed);
> > +    }
> > +    QLIST_FOREACH_SAFE(other_job, &txn->jobs, txn_list, next) {
> > +        ctx = bdrv_get_aio_context(other_job->bs);
> > +        block_job_completed_single(other_job);
> > +        aio_context_release(ctx);
> > +    }
> > +}
> > +
> > +static void block_job_completed_txn_success(BlockJob *job)
> > +{
> > +    AioContext *ctx;
> > +    BlockJobTxn *txn = job->txn;
> > +    BlockJob *other_job, *next;
> > +    /*
> > +     * Successful completion, see if there are other running jobs in this
> > +     * txn.
> > +     */
> > +    QLIST_FOREACH(other_job, &txn->jobs, txn_list) {
> > +        if (!other_job->completed) {
> > +            return;
> > +        }
> > +    }
> > +    /* We are the last completed job, commit the transaction. */
> > +    QLIST_FOREACH_SAFE(other_job, &txn->jobs, txn_list, next) {
> > +        ctx = bdrv_get_aio_context(other_job->bs);
> > +        aio_context_acquire(ctx);
> > +        assert(other_job->ret == 0);
> 
> Sorry for being a dense noggin about this, but is it documented anywhere
> (through an assertion or otherwise) that we will never return a
> positive, non-zero return code for a block job?
> 
> I just don't want to get into a situation where, in the future, someone
> decides to do so and then mysteriously something breaks a version or two
> later.

No, I don't think it's documented. And yes we should document it.

Anyway if someone decides to do so he will hit the assertion here immediately,
instead of a version or two later.

Fam

  reply	other threads:[~2015-09-24  8:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22  2:46 [Qemu-devel] [PATCH v7 00/14] block: incremental backup transactions using BlockJobTxn Fam Zheng
2015-09-22  2:46 ` [Qemu-devel] [PATCH v7 01/14] qapi: Add transaction support to block-dirty-bitmap operations Fam Zheng
2015-09-22  2:46 ` [Qemu-devel] [PATCH v7 02/14] iotests: add transactional incremental backup test Fam Zheng
2015-09-22  2:46 ` [Qemu-devel] [PATCH v7 03/14] block: rename BlkTransactionState and BdrvActionOps Fam Zheng
2015-09-22  2:46 ` [Qemu-devel] [PATCH v7 04/14] backup: Extract dirty bitmap handling as a separate function Fam Zheng
2015-09-22  2:46 ` [Qemu-devel] [PATCH v7 05/14] blockjob: Introduce reference count Fam Zheng
2015-09-22  2:46 ` [Qemu-devel] [PATCH v7 06/14] blockjob: Add .commit and .abort block job actions Fam Zheng
2015-09-22  2:46 ` [Qemu-devel] [PATCH v7 07/14] blockjob: Add "completed" and "ret" in BlockJob Fam Zheng
2015-09-22  2:46 ` [Qemu-devel] [PATCH v7 08/14] blockjob: Simplify block_job_finish_sync Fam Zheng
2015-09-22  2:46 ` [Qemu-devel] [PATCH v7 09/14] block: Add block job transactions Fam Zheng
2015-09-22 19:09   ` John Snow
2015-09-24  8:29     ` Fam Zheng [this message]
2015-09-22  2:46 ` [Qemu-devel] [PATCH v7 10/14] blockdev: make BlockJobTxn available to qmp 'transaction' Fam Zheng
2015-09-22 19:13   ` John Snow
2015-09-22  2:46 ` [Qemu-devel] [PATCH v7 11/14] block/backup: support block job transactions Fam Zheng
2015-09-22 16:03   ` Eric Blake
2015-09-22 21:08   ` John Snow
2015-09-22 22:34     ` Eric Blake
2015-09-22 23:27       ` John Snow
2015-09-23 11:09         ` Markus Armbruster
2015-09-23 16:14           ` John Snow
2015-09-24  6:34             ` Markus Armbruster
2015-09-25 16:05               ` John Snow
2015-09-22  2:46 ` [Qemu-devel] [PATCH v7 12/14] iotests: 124 - transactional failure test Fam Zheng
2015-09-22  2:46 ` [Qemu-devel] [PATCH v7 13/14] qmp-commands.hx: Update the supported 'transaction' operations Fam Zheng
2015-09-30 18:56   ` John Snow
2015-10-01 10:57     ` Kashyap Chamarthy
2015-09-22  2:46 ` [Qemu-devel] [PATCH v7 14/14] tests: add BlockJobTxn unit test Fam Zheng
2015-09-22 23:33   ` John Snow
2015-09-22 20:48 ` [Qemu-devel] [PATCH v7 00/14] block: incremental backup transactions using BlockJobTxn John Snow

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=20150924082902.GA24855@localhost.nay.redhat.com \
    --to=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@parallels.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.