[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87fus9k20i.fsf@vitty.brq.redhat.com>
Date: Sun, 19 Jun 2016 10:37:33 +0200
From: Vitaly Kuznetsov <vkuznets@...hat.com>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
devel@...uxdriverproject.org, Bjorn Helgaas <bhelgaas@...gle.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Jake Oshins <jakeo@...rosoft.com>
Subject: Re: [PATCH 0/2] PCI: hv: fix a couple of issues in hv_pci_onchannelcallback()
Bjorn Helgaas <helgaas@...nel.org> writes:
> On Fri, Jun 10, 2016 at 06:53:36PM -0500, Bjorn Helgaas wrote:
>> On Mon, May 30, 2016 at 04:17:57PM +0200, Vitaly Kuznetsov wrote:
>> > kmemleak helped me to identify a memory leak in hv_pci_onchannelcallback()
>> > and while fixing it I stumbled upon an unrelated issue(s) there.
>> >
>> > Vitaly Kuznetsov (2):
>> > PCI: hv: don't leak buffer in hv_pci_onchannelcallback()
>> > PCI: hv: handle all pending messages in hv_pci_onchannelcallback()
>>
>> I applied both to for-linus for v4.7 with Jake's acks, thanks, Vitaly.
>
> Somehow I must have been thinking these were fixes for things we
> merged or broke during the v4.7 merge window, but that doesn't look
> like the case. So I'm going to merge these for v4.8 instead, on the
> theory that the v4.7-rc cycles are primarily for stabilization.
Right, this is not a 4.7 regression.
Thanks!
--
Vitaly
Powered by blists - more mailing lists