The pull request consists of the below changes:
1) I reverted the old version of hv_sock driver and cherry-picked the upstream version of the driver, and the related bug fixes in hv_sock and vmbus drivers;
2) To further fix the rescind-handling, I cherry-picked a patch from KY, and I made the patch "
UBUNTU: SAUCE: vmbus: unregister device_obj->channels_kset" (which hasn't been in any upstream repo as of today). With the 2 patches, issue #1 and #2 are fixed.
3) I cherry-pick "PCI: hv: Use effective affinity mask" to fix the issue #3.
To resolve the above 3 issues, I created this pull request based on Ubuntu- azure-edge- 4.13.0- 1005.5 (https:/ /git.launchpad. net/~canonical- kernel/ ubuntu/ +source/ linux-azure/ commit/ ?h=azure- edge-next& id=ec62f77bbe06 97ce128f71fac4f c45c99b6f40d1).
The pull request is hosted in my own git repo: /github. com/dcui/ linux/compare/ ec62f77bbe0697c e128f71fac4fc45 c99b6f40d1. ..dcui: decui/azure- edge-next- Ubuntu- azure-edge- 4.13.0- 1005.5- 20171204
https:/
The pull request consists of the below changes:
1) I reverted the old version of hv_sock driver and cherry-picked the upstream version of the driver, and the related bug fixes in hv_sock and vmbus drivers;
2) To further fix the rescind-handling, I cherry-picked a patch from KY, and I made the patch " obj->channels_ kset" (which hasn't been in any upstream repo as of today). With the 2 patches, issue #1 and #2 are fixed.
UBUNTU: SAUCE: vmbus: unregister device_
3) I cherry-pick "PCI: hv: Use effective affinity mask" to fix the issue #3.