[Hyper-V] hvsock: add proper sync for vmbus_hvsock_device_unregister()

Bug #1721576 reported by Joshua R. Poulson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-azure (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

These two patches are needed for hvsock in linux-azure, and are on their way upstream as well:

[PATCH] Revert "vmbus: destroy a hv_sock device only after the
 RESCIND_OFFER is received"
https://github.com/dcui/linux/commit/c15d7f606f813b8d1f1ce02979929fd875da228b.patch

[PATCH] vmbus: hvsock: add proper sync for
 vmbus_hvsock_device_unregister()
https://github.com/dcui/linux/commit/b6ffb4393fb266711b37ed056487665d8650f31a.patch

Joshua R. Poulson (jrp)
Changed in linux-azure (Ubuntu):
status: New → Confirmed
Revision history for this message
Dexuan Cui (decui) wrote :

We actually only need one patch here. I have posted it to LKML: https://patchwork.kernel.org/patch/9995011/

Revision history for this message
Dexuan Cui (decui) wrote :

However, when I look at the 4.11 ubuntu-azure kernel (https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/log/?h=master-next), I think we need to pull more related vmbus patches from the mainline, because there are already non-trivial differences.

Since we're moving to 4.13 (https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/log/?h=azure-edge-next), I'm not sure if we should pull non-trivial changes to the 4.11 ubuntu-azure kernel.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.