qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, jsnow@redhat.com, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block: for jobs, do not clear user_paused until after the resume
Date: Wed, 15 Aug 2018 17:30:54 -0400	[thread overview]
Message-ID: <20180815213054.GF3254@localhost.localdomain> (raw)
In-Reply-To: <79de10c5-28fb-5be2-3141-f09fb4bb5f09@redhat.com>

On Wed, Aug 15, 2018 at 04:25:16PM -0500, Eric Blake wrote:
> On 08/15/2018 10:59 AM, Jeff Cody wrote:
> >The function job_cancel_async() will always cause an assert for blockjob
> >user resume.  We set job->user_paused to false, and then call
> >job->driver->user_resume().  In the case of blockjobs, this is the
> >block_job_user_resume() function.
> >
> >In that function, we assert that job.user_paused is set to true.
> >Unfortunately, right before calling this function, it has explicitly
> >been set to false.
> >
> >The fix is pretty simple: set job->user_paused to false only after the
> >job user_resume() function has been called.
> >
> >Signed-off-by: Jeff Cody <jcody@redhat.com>
> >---
> >  job.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> 
> Does this need to CC qemu-stable?
> 

Good point, yes.  I'm going to do a v2 with an iotest, and I'll CC
qemu-stable on that one.

> Reviewed-by: Eric Blake <eblake@redhat.com>
> 

Thanks


-Jeff

      reply	other threads:[~2018-08-15 21:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15 15:59 [Qemu-devel] [PATCH] block: for jobs, do not clear user_paused until after the resume Jeff Cody
2018-08-15 21:23 ` John Snow
2018-08-15 21:31   ` Jeff Cody
2018-08-15 21:25 ` Eric Blake
2018-08-15 21:30   ` Jeff Cody [this message]

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=20180815213054.GF3254@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jsnow@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 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).