qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 07/11] blockjob: introduce block_job_cancel_async, check iostatus invariants
Date: Thu, 27 Apr 2017 10:20:27 +0200	[thread overview]
Message-ID: <f3d9c513-444b-c0d1-8967-3430fe63776c@redhat.com> (raw)
In-Reply-To: <e733d2b3-4c20-e9a4-4807-86675661f2cc@redhat.com>



On 26/04/2017 22:25, John Snow wrote:
>>  
>>  void block_job_iostatus_reset(BlockJob *job)
>>  {
>> +    if (job->iostatus == BLOCK_DEVICE_IO_STATUS_OK) {
>> +        return;
>> +    }
>> +    assert(job->user_paused && job->pause_count > 0);
> Why assert that it's user-paused? Will that be true from:
> 
> (A) All users of block_job_cancel_async, including:
> 
> - block_job_cancel
> - block_job_completed
>     block_job_completed_txn_abort
> 
> (B) all users of blk_iostatus_reset:
> - blk_do_attach_dev
> - qmp_cont
> 
> It's ... not really clear to me that this is true, can you help me out?

Setting iostatus to not-ok only happens in block_job_iostatus_set_err, 
which is called from block_job_error_action:

    if (action == BLOCK_ERROR_ACTION_STOP) {
        /* make the pause user visible, which will be resumed from QMP. */
        block_job_user_pause(job);
        block_job_iostatus_set_err(job, error);
    }

Paolo
Paolo

  reply	other threads:[~2017-04-27  8:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 14:42 [Qemu-devel] [PATCH for 2.10 00/11] Preparation for block job mutex Paolo Bonzini
2017-04-19 14:42 ` [Qemu-devel] [PATCH 01/11] blockjob: remove unnecessary check Paolo Bonzini
2017-04-19 15:48   ` Eric Blake
2017-04-19 16:12     ` Paolo Bonzini
2017-04-19 16:16       ` Eric Blake
2017-04-24 23:19   ` John Snow
2017-04-26  8:36     ` Paolo Bonzini
2017-04-19 14:42 ` [Qemu-devel] [PATCH 02/11] blockjob: remove iostatus_reset callback Paolo Bonzini
2017-04-19 14:42 ` [Qemu-devel] [PATCH 03/11] blockjob: introduce block_job_early_fail Paolo Bonzini
2017-04-19 14:42 ` [Qemu-devel] [PATCH 04/11] blockjob: introduce block_job_pause/resume_all Paolo Bonzini
2017-04-19 14:42 ` [Qemu-devel] [PATCH 05/11] blockjob: separate monitor and blockjob APIs Paolo Bonzini
2017-04-24 23:24   ` John Snow
2017-05-04 10:50   ` Stefan Hajnoczi
2017-04-19 14:42 ` [Qemu-devel] [PATCH 06/11] blockjob: move iostatus reset inside block_job_user_resume Paolo Bonzini
2017-04-19 14:42 ` [Qemu-devel] [PATCH 07/11] blockjob: introduce block_job_cancel_async, check iostatus invariants Paolo Bonzini
2017-04-26 20:25   ` John Snow
2017-04-27  8:20     ` Paolo Bonzini [this message]
2017-05-04 10:53   ` Stefan Hajnoczi
2017-04-19 14:42 ` [Qemu-devel] [PATCH 08/11] blockjob: group BlockJob transaction functions together Paolo Bonzini
2017-04-24 23:46   ` John Snow
2017-05-04 10:53   ` Stefan Hajnoczi
2017-04-19 14:42 ` [Qemu-devel] [PATCH 09/11] blockjob: strengthen a bit test-blockjob-txn Paolo Bonzini
2017-04-19 14:42 ` [Qemu-devel] [PATCH 10/11] blockjob: reorganize block_job_completed_txn_abort Paolo Bonzini
2017-05-04 10:59   ` Stefan Hajnoczi
2017-04-19 14:42 ` [Qemu-devel] [PATCH 11/11] blockjob: use deferred_to_main_loop to indicate the coroutine has ended Paolo Bonzini
2017-05-04 11:07   ` Stefan Hajnoczi
2017-05-04 11:07   ` Stefan Hajnoczi
  -- strict thread matches above, loose matches on Subject: below --
2017-05-08 14:12 [Qemu-devel] [PATCH v2 00/11] Preparation for block job mutex Paolo Bonzini
2017-05-08 14:13 ` [Qemu-devel] [PATCH 07/11] blockjob: introduce block_job_cancel_async, check iostatus invariants Paolo Bonzini

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=f3d9c513-444b-c0d1-8967-3430fe63776c@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jsnow@redhat.com \
    --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 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).