linux-kernel - [PATCH 000/206] Staging: hv: Cleanup hv drivers

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: <1304978242-22958-1-git-send-email-kys@microsoft.com>
Date:	Mon,  9 May 2011 14:57:22 -0700
From:	"K. Y. Srinivasan" <kys@...rosoft.com>
To:	gregkh@...e.de, linux-kernel@...r.kernel.org,
	devel@...uxdriverproject.org, virtualization@...ts.osdl.org
Cc:	"K. Y. Srinivasan" <kys@...rosoft.com>
Subject: [PATCH 000/206] Staging: hv: Cleanup hv drivers 

This patch-set deals with some of the architectural isues in all of
the Hyper-V drivers. Specifically:

	1) Fixes a number of locking issues in the block driver.

	2) Eliminates all the indirection through the hv_driver
	   abstraction.

	3) Simplifies the code across the board eliminating 
	   unnecessary code and data structure layering. Prior to
	   this restructuring there were about 11,000 lines of code
	   in the hv directory. After this cleanup, there are about
	   8500 lines of code.

	4) I have dealt with style and naming issues across all the drivers.

	5) All the header files have been cleaned up and consolidated:
		1) A single header file include/linux/hyperv.h. This file
		   is to be included in all the drivers that attach to the
		   vmbus.

		2) A single header file that has all the defines for building
		   the vmbus driver.
		3) Consolidate header files for each device class -
		   disk and net.


Regads,

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/