[Bug 1747970] Re: [Hyper-V] vsock: always call vsock_init_tables()

2018-02-21 Thread Nivedita Singhvi
Any other backports needed, Marcelo and Josh?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747970

Title:
  [Hyper-V] vsock: always call vsock_init_tables()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1747970/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1747970] Re: [Hyper-V] vsock: always call vsock_init_tables()

2018-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 4.13.0-1011.14

---
linux-azure (4.13.0-1011.14) xenial; urgency=medium

  * linux-azure: 4.13.0-1011.14 -proposed tracker (LP: #1748476)

  * [Hyper-V] Fixes for Network Direct InfiniBand/RDMA driver (LP: #1749332)
- SAUCE: vmbus-rdma: ND142: don't wait forever for disconnection from remote
  connector
- SAUCE: vmbus-rdma: ND142: remove idr handle before calling ND on freeing 
CQ
  and QP
- SAUCE: vmbus-rdma: ND142: do not crash on idr allocation failure - warn
  instead
- SAUCE: vmbus-rdma: ND144: don't wait forever for disconnection from remote
  connector
- SAUCE: vmbus-rdma: ND144: remove idr handle before calling ND on freeing 
CQ
  and QP
- SAUCE: vmbus-rdma: ND144: do not crash on idr allocation failure - warn
  instead

  * [Hyper-V] vsock: always call vsock_init_tables() (LP: #1747970)
- vsock: always call vsock_init_tables()

  * Update the source code location in the debian package for cloud kernels
(LP: #1747890)
- [Debian] Update git repository URI

  [ Ubuntu: 4.13.0-35.39 ]

  * linux: 4.13.0-35.39 -proposed tracker (LP: #1748743)
  * CVE-2017-5715 (Spectre v2 Intel)
- Revert "UBUNTU: SAUCE: turn off IBPB when full retpoline is present"
- SAUCE: turn off IBRS when full retpoline is present
- [Packaging] retpoline files must be sorted
- [Packaging] pull in retpoline files

  [ Ubuntu: 4.13.0-34.37 ]

  * linux: 4.13.0-34.37 -proposed tracker (LP: #1748475)
  * libata: apply MAX_SEC_1024 to all LITEON EP1 series devices (LP: #1743053)
- libata: apply MAX_SEC_1024 to all LITEON EP1 series devices
  * KVM patches for s390x to provide facility bits 81 (ppa15) and 82 (bpb)
(LP: #1747090)
- KVM: s390: wire up bpb feature
  * artful 4.13 i386 kernels crash after memory hotplug remove (LP: #1747069)
- Revert "mm, memory_hotplug: do not associate hotadded memory to zones 
until
  online"
  * CVE-2017-5715 (Spectre v2 Intel)
- x86/feature: Enable the x86 feature to control Speculation
- x86/feature: Report presence of IBPB and IBRS control
- x86/enter: MACROS to set/clear IBRS and set IBPB
- x86/enter: Use IBRS on syscall and interrupts
- x86/idle: Disable IBRS entering idle and enable it on wakeup
- x86/idle: Disable IBRS when offlining cpu and re-enable on wakeup
- x86/mm: Set IBPB upon context switch
- x86/mm: Only set IBPB when the new thread cannot ptrace current thread
- x86/entry: Stuff RSB for entry to kernel for non-SMEP platform
- x86/kvm: add MSR_IA32_SPEC_CTRL and MSR_IA32_PRED_CMD to kvm
- x86/kvm: Set IBPB when switching VM
- x86/kvm: Toggle IBRS on VM entry and exit
- x86/spec_ctrl: Add sysctl knobs to enable/disable SPEC_CTRL feature
- x86/spec_ctrl: Add lock to serialize changes to ibrs and ibpb control
- x86/cpu/AMD: Add speculative control support for AMD
- x86/microcode: Extend post microcode reload to support IBPB feature
- KVM: SVM: Do not intercept new speculative control MSRs
- x86/svm: Set IBRS value on VM entry and exit
- x86/svm: Set IBPB when running a different VCPU
- KVM: x86: Add speculative control CPUID support for guests
- SAUCE: turn off IBPB when full retpoline is present
  * Artful 4.13 fixes for tun (LP: #1748846)
- tun: call dev_get_valid_name() before register_netdevice()
- tun: allow positive return values on dev_get_valid_name() call
- tun/tap: sanitize TUNSETSNDBUF input
  * boot failure on AMD Raven + WestonXT (LP: #1742759)
- SAUCE: drm/amdgpu: add atpx quirk handling (v2)

linux-azure (4.13.0-1010.13) xenial; urgency=low

  * linux-azure: 4.13.0-1010.13 -proposed tracker (LP: #1746907)

  * CVE-2017-5715 (Spectre v2 retpoline)
- x86/retpoline/hyperv: Convert assembler indirect jumps
- [Config] azure: enable CONFIG_GENERIC_CPU_VULNERABILITIES
- [Config] azure: enable CONFIG_RETPOLINE
- [Config] azure: disable retpoline checks for first upload

  * Update the source code location in the debian package for cloud kernels
(LP: #1747890)
- [Debian] Update git repository URI

  * [Hyper-V] linux-azure: PCI: hv: Do not sleep in compose_msi_msg()
(LP: #1747543)
- PCI: hv: Do not sleep in compose_msi_msg()

  [ Ubuntu: 4.13.0-33.36 ]

  * linux: 4.13.0-33.36 -proposed tracker (LP: #1746903)
  * starting VMs causing retpoline4 to reboot (LP: #1747507) // CVE-2017-5715
(Spectre v2 retpoline)
- x86/retpoline: Fill RSB on context switch for affected CPUs
- x86/retpoline: Add LFENCE to the retpoline/RSB filling RSB macros
- x86/retpoline: Optimize inline assembler for vmexit_fill_RSB
- x86/retpoline: Remove the esp/rsp thunk
- x86/retpoline: Simplify vmexit_fill_RSB()
  * Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC
(LP: #1743638)
- [d-i] Add qede to nic-modules udeb
  * hisi_sas: driver robustness fixes (LP: #1739807)
- scsi: 

[Bug 1747970] Re: [Hyper-V] vsock: always call vsock_init_tables()

2018-02-15 Thread Marcelo Cerri
** Changed in: linux-azure (Ubuntu Xenial)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747970

Title:
  [Hyper-V] vsock: always call vsock_init_tables()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1747970/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1747970] Re: [Hyper-V] vsock: always call vsock_init_tables()

2018-02-14 Thread Marcelo Cerri
Josh, should this change also be applied to the generic kernels?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747970

Title:
  [Hyper-V] vsock: always call vsock_init_tables()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1747970/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1747970] Re: [Hyper-V] vsock: always call vsock_init_tables()

2018-02-08 Thread Marcelo Cerri
https://lists.ubuntu.com/archives/kernel-team/2018-February/090082.html

** Changed in: linux-azure-edge (Ubuntu Xenial)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747970

Title:
  [Hyper-V] vsock: always call vsock_init_tables()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1747970/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1747970] Re: [Hyper-V] vsock: always call vsock_init_tables()

2018-02-08 Thread Marcelo Cerri
** Changed in: linux-azure (Ubuntu Xenial)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: linux-azure (Ubuntu Xenial)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747970

Title:
  [Hyper-V] vsock: always call vsock_init_tables()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1747970/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1747970] Re: [Hyper-V] vsock: always call vsock_init_tables()

2018-02-08 Thread Stefan Bader
** Also affects: linux-azure (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-azure-edge (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747970

Title:
  [Hyper-V] vsock: always call vsock_init_tables()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1747970/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1747970] Re: [Hyper-V] vsock: always call vsock_init_tables()

2018-02-08 Thread Marcelo Cerri
** Also affects: linux-azure-edge (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747970

Title:
  [Hyper-V] vsock: always call vsock_init_tables()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1747970/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1747970] Re: [Hyper-V] vsock: always call vsock_init_tables()

2018-02-07 Thread Dexuan Cui
Yes, I confirm this is the patch we need for the Enhanced Session mode.

The patch was originally made to fix a different issue, but it can also
fix the VM panic we see with Enhanced Session mode, because the cause is
the same: there is a race

static int __init hvs_init(void)
{
int ret;

if (vmbus_proto_version < VERSION_WIN10)
return -ENODEV;

ret = vmbus_driver_register(_drv);
if (ret != 0)
return ret;
Dexuan: ---: if the host-initiated connection comes 
here (e.g. before we call vsock_core_init(),  hvs_open_connection() -> 
vsock_find_bound_socket() -> __vsock_find_bound_socket() can access the 
uninitialized vsock_bound_sockets(addr) -> vsock_bind_table, which will be 
initialized in vsock_core_init() -> vsock_init_tables(), and we'll hit a panic.

ret = vsock_core_init(_transport);
if (ret) {
vmbus_driver_unregister(_drv);
return ret;
}

return 0;
}


The latest  upstream 4.15.1 kernel has the fix already, but 4.14.17 doesn't 
have the fix.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747970

Title:
  [Hyper-V] vsock: always call vsock_init_tables()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1747970/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs