From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Dexuan Cui <decui@microsoft.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
"olaf@aepfle.de" <olaf@aepfle.de>,
Rolf Neugebauer <rolf.neugebauer@docker.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"apw@canonical.com" <apw@canonical.com>
Subject: Re: [PATCH] Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read()
Date: Thu, 26 Jan 2017 08:49:17 +0100 [thread overview]
Message-ID: <20170126074917.GA21753@kroah.com> (raw)
In-Reply-To: <MWHPR03MB2669FE7A96A50113199F0D60BF770@MWHPR03MB2669.namprd03.prod.outlook.com>
On Thu, Jan 26, 2017 at 07:44:46AM +0000, Dexuan Cui wrote:
> > From: gregkh@linuxfoundation.org [mailto:gregkh@linuxfoundation.org]
> > > Dexuan Cui <decui@microsoft.com> wrote:
> > > As I checked against the kernels listed on the homapage,
> > > the below versions are impacted:
> > > v3.16.39
> > > v3.18.47
> > > v4.1.38
> > > v4.8.17
> > > v4.9.5
> > > v4.10-rc5
> > >
> > > It's interesting v4.4.44 is not impacted, but actually it needs both the 2 patches:
> > > i.e. this patch, and the previous one:
> > > Commit a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in
> > hv_need_to_signal_on_read()")
> >
> > That patch does not apply to the 4.4-stable tree, which is why it was
> > not included there. If you feel it should be included, please provide a
> > backport and send it to the stable@vger.kernel.org mailing list.
> >
> > greg k-h
>
> Thanks! I'll do the backport after this patch goes in the mainline.
Why wait?
next prev parent reply other threads:[~2017-01-26 7:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 6:54 [PATCH] Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read() Dexuan Cui
2017-01-24 16:08 ` Stephen Hemminger
2017-01-26 6:10 ` Dexuan Cui
2017-01-26 7:16 ` gregkh
2017-01-26 7:44 ` Dexuan Cui
2017-01-26 7:49 ` gregkh [this message]
2017-01-26 8:27 ` Dexuan Cui
2017-01-26 9:16 ` gregkh
2017-01-26 9:31 ` Dexuan Cui
2017-01-26 10:10 ` gregkh
2017-01-26 10:24 ` Dexuan Cui
2017-01-26 10:28 ` gregkh
2017-01-26 10:31 ` Dexuan Cui
2017-01-26 19:16 ` 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=20170126074917.GA21753@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=decui@microsoft.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=rolf.neugebauer@docker.com \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.com \
/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.