linux-kernel - Re: [PATCH 1/6] Drivers: hv: vmbus: Perform device register in the per-channel work element

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 linux-cve-announce 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, 12 Mar 2015 10:02:24 +0100
From:	Greg KH <gregkh@...uxfoundation.org>
To:	"K. Y. Srinivasan" <kys@...rosoft.com>
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 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?

thanks,

greg k-h
--
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/