Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: kys@microsoft.com, haiyang@microsoft.com
Cc: devel@linuxdriverproject.org, stable@vger.kernel.org,
	Greg KH <greg@kroah.com>
Subject: Re: [PATCH] vmbus: re-enable tasklet
Date: Thu, 29 Jun 2017 16:31:20 -0700	[thread overview]
Message-ID: <20170629163120.42d75fc3@xeon-e3> (raw)
In-Reply-To: <20170622231654.14474-1-sthemmin@microsoft.com>

On Thu, 22 Jun 2017 16:16:54 -0700
Stephen Hemminger <stephen@networkplumber.org> wrote:

> This problem shows up in 4.11 when netvsc driver is removed and reloaded.
> The problem is that the channel is closed during module removal and the
> tasklet for processing responses is disabled. When module is reloaded
> the channel is reopened but the tasklet is marked as disabled.
> 
> Patch for upstream is pending, but less urgent since problem doesn't
> happen with network driver in 4.12.
> 
> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
> ---
>  drivers/hv/channel.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c
> index 321b8833fa6f..36c9ce191b74 100644
> --- a/drivers/hv/channel.c
> +++ b/drivers/hv/channel.c
> @@ -606,6 +606,8 @@ static int vmbus_close_internal(struct vmbus_channel *channel)
>  		get_order(channel->ringbuffer_pagecount * PAGE_SIZE));
>  
>  out:
> +	/* re-enable tasklet for use on re-open */
> +	tasklet_enable(&channel->callback_event);
>  	return ret;
>  }
>  

Ping.

What is the state of this patch? Why is it not queued for 4.11 stable?

  reply	other threads:[~2017-06-29 23:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 23:16 [PATCH] vmbus: re-enable tasklet Stephen Hemminger
2017-06-29 23:31 ` Stephen Hemminger [this message]
2017-06-29 23:35   ` KY Srinivasan
2017-06-30  3:27     ` KY Srinivasan

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=20170629163120.42d75fc3@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=devel@linuxdriverproject.org \
    --cc=greg@kroah.com \
    --cc=haiyang@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=stable@vger.kernel.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