From: Stephen Hemminger <stephen@networkplumber.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Dexuan Cui <decui@microsoft.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
KY Srinivasan <kys@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [PATCH] vmbus: fix missing signaling in hv_signal_on_read()
Date: Wed, 6 Sep 2017 21:32:54 -0700 [thread overview]
Message-ID: <20170906213254.3b8ea35c@xeon-e3> (raw)
In-Reply-To: <20170907042725.GA17231@kroah.com>
On Thu, 7 Sep 2017 06:27:25 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:
> On Thu, Sep 07, 2017 at 12:54:09AM +0000, Dexuan Cui wrote:
> > > From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> > > Sent: Wednesday, August 16, 2017 9:16 AM
> > > To: Greg KH <gregkh@linuxfoundation.org>
> > > Cc: KY Srinivasan <kys@microsoft.com>; Dexuan Cui <decui@microsoft.com>;
> > > devel@linuxdriverproject.org; linux-kernel@vger.kernel.org;
> > > stable@vger.kernel.org; Stephen Hemminger <sthemmin@microsoft.com>;
> > > John Starks <jon.Starks@microsoft.com>
> > > Subject: Re: [PATCH] vmbus: fix missing signaling in hv_signal_on_read()
> > >
> > > On Wed, 16 Aug 2017 09:10:40 -0700
> > > Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > > > On Wed, Aug 16, 2017 at 08:49:46AM -0700, Stephen Hemminger wrote:
> > > > > When the space available before start of reading (cached_write_sz)
> > > > > is the same as the host required space (pending_sz), we need to
> > > > > still signal host.
> > > > >
> > > > > Fixes: 433e19cf33d3 ("Drivers: hv: vmbus: finally fix
> > > hv_need_to_signal_on_read()")
> > > > >
> > > > > Signed-off-by: John Starks <jon.Starks@microsoft.com>
> > > > > Signed-off-by: Dexuan Cui <decui@microsoft.com>
> > > > > Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
> > > > > ---
> > > > > This patch is for 4.13 (and stable).
> > > > > A different fix is needed for linux-next.
> > > >
> > > > Is there a fix for this in Linus's tree? If so, what's the git commit
> > > > id? We need to wait for that until I can take it in -stable.
> > >
> > > There is no commit yet in Linus's tree. Was submitting for both Linus
> > > and stable. Wasn't sure about the timing since 4.13 might close before he gets
> > > to it.
> >
> > Hi Greg and stable@vger.kernel.org,
> > We need the patch for the stable kernels: v4.13, v4.12.10 and v4.9.47.
> >
> > The patch is not in Linus's tree, because the bug is resolved there by a series
> > of 4 patches (see the below).
> >
> > IMO it's better to apply this small patch to the stable kernels rather than
> > backporting the 4 big commits?
>
> It is always better to backport the original commits. Will they work
> as-is, or do they need porting?
I will try for 4.13 but going back to 4.9 might be hard.
next prev parent reply other threads:[~2017-09-07 4:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 15:49 [PATCH] vmbus: fix missing signaling in hv_signal_on_read() Stephen Hemminger
2017-08-16 16:10 ` Greg KH
2017-08-16 16:16 ` Stephen Hemminger
2017-09-07 0:54 ` Dexuan Cui
2017-09-07 4:27 ` Greg KH
2017-09-07 4:32 ` Stephen Hemminger [this message]
2017-09-07 15:41 ` Stephen Hemminger
2017-10-10 15:01 ` Greg KH
2017-10-11 16:55 ` Stephen Hemminger
2017-10-11 18:09 ` KY Srinivasan
2017-10-13 17:55 ` Dexuan Cui
2017-10-19 13:12 ` Greg KH
2017-10-19 18:15 ` Dexuan Cui
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=20170906213254.3b8ea35c@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=decui@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=kys@microsoft.com \
--cc=stable@vger.kernel.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 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).