All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
	roger.pau@citrix.com
Subject: Re: [PATCH] xen-blkback: clear PF_NOFREEZE for xen_blkif_schedule()
Date: Mon, 7 Dec 2015 17:00:22 -0500	[thread overview]
Message-ID: <20151207220022.GA6958@char.us.oracle.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1510261445300.8998@pobox.suse.cz>

On Mon, Oct 26, 2015 at 02:47:21PM +0900, Jiri Kosina wrote:
> From: Jiri Kosina <jkosina@suse.cz>
> 
> xen_blkif_schedule() kthread calls try_to_freeze() at the beginning of 
> every attempt to purge the LRU. This operation can't ever succeed though, 
> as the kthread hasn't marked itself as freezable.

<nods>!
> 
> Before (hopefully eventually) kthread freezing gets converted to fileystem 
> freezing, we'd rather mark xen_blkif_schedule() freezable (as it can 
> generate I/O during suspend).
> 
> Signed-off-by: Jiri Kosina <jkosina@suse.cz>

Thank you for reporting that. Will queue it up for Linux 4.5!
> ---
>  drivers/block/xen-blkback/blkback.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/block/xen-blkback/blkback.c b/drivers/block/xen-blkback/blkback.c
> index af3caa3..bb65f7c 100644
> --- a/drivers/block/xen-blkback/blkback.c
> +++ b/drivers/block/xen-blkback/blkback.c
> @@ -597,6 +597,7 @@ int xen_blkif_schedule(void *arg)
>  
>  	xen_blkif_get(blkif);
>  
> +	set_freezable();
>  	while (!kthread_should_stop()) {
>  		if (unlikely(vbd->size != vbd_sz(vbd)))
>  			xen_vbd_resize(blkif);
> 
> -- 
> Jiri Kosina
> SUSE Labs

  reply	other threads:[~2015-12-07 22:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26  5:47 [PATCH] xen-blkback: clear PF_NOFREEZE for xen_blkif_schedule() Jiri Kosina
2015-12-07 22:00 ` Konrad Rzeszutek Wilk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-26  5:47 Jiri Kosina

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=20151207220022.GA6958@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=jikos@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.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.