[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY2PR0301MB07112E8E14999AA2EA2784A9A0060@BY2PR0301MB0711.namprd03.prod.outlook.com>
Date: Thu, 12 Mar 2015 13:12:29 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"olaf@...fle.de" <olaf@...fle.de>,
"apw@...onical.com" <apw@...onical.com>,
"vkuznets@...hat.com" <vkuznets@...hat.com>
Subject: RE: [PATCH 1/6] Drivers: hv: vmbus: Perform device register in the
per-channel work element
> -----Original Message-----
> From: Greg KH [mailto:gregkh@...uxfoundation.org]
> Sent: Thursday, March 12, 2015 2:03 AM
> To: KY Srinivasan
> Cc: linux-kernel@...r.kernel.org; devel@...uxdriverproject.org;
> olaf@...fle.de; apw@...onical.com; vkuznets@...hat.com
> Subject: Re: [PATCH 1/6] Drivers: hv: vmbus: Perform device register in the
> per-channel work element
>
> On Thu, Mar 12, 2015 at 10:02:24AM +0100, Greg KH wrote:
> > On Wed, Mar 11, 2015 at 06:56:54PM -0700, K. Y. Srinivasan wrote:
> > > This patch is a continuation of the rescind handling cleanup work.
> > > We cannot block in the global message handling work context
> > > especially if we are blocking waiting for the host to wake us up. I
> > > would like to thank Dexuan Cui <decui@...rosoft.com> for observing
> this problem.
> > >
> > > The current Linux 4.0 RC3 tree is broken and this patch fixes the problem.
> > >
> > > Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com>
> > > ---
> > > drivers/hv/channel_mgmt.c | 143
> +++++++++++++++++++++++++++++++-------------
> > > drivers/hv/connection.c | 6 ++-
> > > drivers/hv/hyperv_vmbus.h | 2 +-
> > > 3 files changed, 107 insertions(+), 44 deletions(-)
> >
> > This is a very big patch so late in the -rc cycle. Is there some
> > patch that got merged in 4.0-rc1 that I should be reverting instead to
> > fix things up?
>
> Make that, "this is a very large patch set", not just one patch. I can't take all
> of these this late, sorry. Please just tell me what to revert.
Greg,
Would it be possible to pick up two patches. I could prune this down to two. The two I want you to
pick up are (in the order of importance):
[PATCH 1/6] Drivers: hv: vmbus: Perform device register in the per-channel work element
[PATCH 2/6] Drivers: hv: hv_balloon: keep locks balanced on add_memory() failure
If you could pickup an additional patch that would be:
[PATCH 6/6] Drivers: hv: vmbus: Fix a bug in rescind processing in vmbus_close_internal()
The first one is the most important one and if you can only pickup one, the first one is the one I want you to pick up.
The third one fixes a memory leak issue that occurs only under
certain conditions. We may have to revert more patches than applying the two patches that
would fix the most important issues.
Let me know if you want me to resend the ones that you can apply.
Thank you in advance,
K. Y
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists