linux-kernel - Re: [PATCH] Drivers: hv: vmbus: finally fix hv_need_to_signal_on

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 26 Jan 2017 11:10:07 +0100
From:   "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To:     Dexuan Cui <decui@...rosoft.com>
Cc:     Stephen Hemminger <stephen@...workplumber.org>,
        "driverdev-devel@...uxdriverproject.org" 
        <driverdev-devel@...uxdriverproject.org>,
        KY Srinivasan <kys@...rosoft.com>,
        Haiyang Zhang <haiyangz@...rosoft.com>,
        Stephen Hemminger <sthemmin@...rosoft.com>,
        "olaf@...fle.de" <olaf@...fle.de>,
        Rolf Neugebauer <rolf.neugebauer@...ker.com>,
        "jasowang@...hat.com" <jasowang@...hat.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "apw@...onical.com" <apw@...onical.com>
Subject: Re: [PATCH] Drivers: hv: vmbus: finally fix
 hv_need_to_signal_on_read()

On Thu, Jan 26, 2017 at 09:31:32AM +0000, Dexuan Cui wrote:
> > From: gregkh@...uxfoundation.org [mailto:gregkh@...uxfoundation.org]
> > > > From: gregkh@...uxfoundation.org [mailto:gregkh@...uxfoundation.org]
> > > > > > > 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@...r.kernel.org mailing list.
> > > > > >
> > > > > > greg k-h
> > > > >
> > > > > Thanks! I'll do the backport after this patch goes in the mainline.
> > > >
> > > > Why wait?
> > >
> > > I thought a patch must first appear in Linus's tree, before it can be
> > > back-ported to the stable tree?
> > 
> > Commit a389fcfd2cb5 _IS_ in Linus's tree, it was released in the 4.7-rc1
> > kernel, which happened in May of 2016.
> > 
> > greg k-h
> 
> Sorry, it looks I didn't make it clear. :-)
> 
> v4.4.44 needs 2 patches, i.e. a389fcfd2cb5, and this patch (which is not in
> Linus's tree yet).  Only backporting the first patch immediately is not enough
> and is also improper IMO, because the first patch introduces a new issue,
> which is being resolved by this patch. So my understanding is that I should
> backport the 2 patches together.

Ok, that makes a bit more sense, thanks.  I'll wait for your "real"
patch to hit Linus's tree then.

greg k-h