From: Greg KH <greg@kroah.com>
To: "Kamata, Munehisa" <kamatam@amazon.com>
Cc: stable@vger.kernel.org, aliguori@amazon.com, 3chas3@gmail.com
Subject: Re: net/xen-netfront patch for stable
Date: Sat, 17 Oct 2015 17:06:15 -0700 [thread overview]
Message-ID: <20151018000615.GB18971@kroah.com> (raw)
In-Reply-To: <5615A7CF.1040106@amazon.com>
On Wed, Oct 07, 2015 at 04:16:31PM -0700, Kamata, Munehisa wrote:
> Hi stable maintainers,
>
> Could you please consider applying the following patch to stable trees? In particular, I think this is needed for 3.18 or later.
>
> 274b045509175db0405c784be85e8cce116e6f7d net/xen-netfront: only napi_synchronize() if running
>
> Without this commit, we found that a migrated Linux guest could go into an infinite loop at boot. We confirmed that the issue went away with v4.1.6 + the commit.
>
Now applied, thanks.
greg k-h
next parent reply other threads:[~2015-10-18 0:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5615A7CF.1040106@amazon.com>
2015-10-18 0:06 ` Greg KH [this message]
2015-10-19 10:53 ` net/xen-netfront patch for stable Luis Henriques
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=20151018000615.GB18971@kroah.com \
--to=greg@kroah.com \
--cc=3chas3@gmail.com \
--cc=aliguori@amazon.com \
--cc=kamatam@amazon.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;
as well as URLs for NNTP newsgroup(s).