Comment 27 for bug 929545

After some internal investigation, this is a known issue in the build of hv_storvsc that is present in the Ubuntu kernel sources, including 3.2.0-16. The latest version of the driver, available in linux-next after Feb 14 (at its new location in /drivers/scsi/storvsc_drv.c) has that resolved, as well as other cleanup issues from the community review.

In fact, I would strongly suggest that the latest hv* drivers from linux-next be used if at all possible. The snapshot being used as the base for the Precise kernel only has the hv_vmbus driver out of staging. With the release of the 3.3 kernel, the hv_netvsc and hv_mouse drivers were approved for exit, and we've already received word that the hv_storvsc driver will exit in 3.4. The quality of code after going through the community review is leaps and bounds better than what is present in 3.2, and should be ideal for a -LTS release.

To accomplish this, you can either pull from linux-next and replace the files in /drivers/staging/hv (which would require no changes to the build system), or pull the appropriate files out of the various folders (as well as the Kconfigs) and place them in the locations as of linux-next:

drivers/hv, drivers/net/hyperv/, drivers/hid/hid-hyperv.c, drivers/scsi/storvsc_drv.c

Please let me know how you'd like to proceed on this.

-M