linux-kernel - [PATCH 0/5] Drivers: hv: vmbus: Cleanup the vmbus unload path

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-next>] [day] [month] [year] [list]

Message-Id: <1429515878-13710-1-git-send-email-kys@microsoft.com>
Date:	Mon, 20 Apr 2015 00:44:38 -0700
From:	"K. Y. Srinivasan" <kys@...rosoft.com>
To:	gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
	devel@...uxdriverproject.org, olaf@...fle.de, apw@...onical.com,
	vkuznets@...hat.com, jasowang@...hat.com
Cc:	"K. Y. Srinivasan" <kys@...rosoft.com>
Subject: [PATCH 0/5] Drivers: hv: vmbus: Cleanup the vmbus unload path

This patch-set have several fixes to enable the clean unload of the vmbus.
Typically, vmbus will not be unloadable when Linux is hosted on
Hyper-V since the driver managing the root device needs the vmbus driver.

Dexuan Cui (1):
  hv: vmbus_free_channels(): remove the redundant free_channel()

K. Y. Srinivasan (2):
  drivers: hv: vmbus: Get rid of some unused definitions
  Drivers: hv: vmbus: Implement the protocol for tearing down vmbus
    state

Vitaly Kuznetsov (2):
  Drivers: hv: vmbus: introduce vmbus_acpi_remove
  Drivers: hv: vmbus: unregister panic notifier on module unload

 drivers/hv/channel_mgmt.c |   36 +++++++++++++++++++++++++++++++++---
 drivers/hv/connection.c   |    5 +++++
 drivers/hv/hyperv_vmbus.h |    2 ++
 drivers/hv/vmbus_drv.c    |   14 ++++++++++++++
 include/linux/hyperv.h    |   20 +-------------------
 5 files changed, 55 insertions(+), 22 deletions(-)

-- 
1.7.4.1

--
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/