Re: [PATCH] x86/paravirt: Guard against invalid cpu # in pv_vcpu_is_preempted()

2019-03-25 Thread Waiman Long
On 03/25/2019 12:40 PM, Juergen Gross wrote: > On 25/03/2019 16:57, Waiman Long wrote: >> It was found that passing an invalid cpu number to pv_vcpu_is_preempted() >> might panic the kernel in a VM guest. For example, >> >> [2.531077] Oops: [#1] SMP PTI >> : >> [2.532545] Hardware na

Re: [PATCH] x86/paravirt: Guard against invalid cpu # in pv_vcpu_is_preempted()

2019-03-25 Thread Juergen Gross
On 25/03/2019 16:57, Waiman Long wrote: > It was found that passing an invalid cpu number to pv_vcpu_is_preempted() > might panic the kernel in a VM guest. For example, > > [2.531077] Oops: [#1] SMP PTI > : > [2.532545] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 > [2.5333

[PATCH] x86/paravirt: Guard against invalid cpu # in pv_vcpu_is_preempted()

2019-03-25 Thread Waiman Long
It was found that passing an invalid cpu number to pv_vcpu_is_preempted() might panic the kernel in a VM guest. For example, [2.531077] Oops: [#1] SMP PTI : [2.532545] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 [2.533321] RIP: 0010:__raw_callee_save___kvm_vcpu_is_preempte

Re: INFO: task hung in vhost_net_stop_vq

2019-03-25 Thread Michael S. Tsirkin
Looks like more iotlb locking mess? On Tue, Mar 19, 2019 at 10:21:00PM -0700, syzbot wrote: > syzbot has bisected this bug to: > > commit 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c > Author: Jason Wang > Date: Thu Jun 23 06:04:32 2016 + > > vhost: new device IOTLB API > > bisection log

Re: [PATCH -next] drm/ttm: remove set but not used variable 'vgdev'

2019-03-25 Thread Daniel Vetter
On Wed, Mar 20, 2019 at 02:03:08AM +, YueHaibing wrote: > Fixes gcc '-Wunused-but-set-variable' warning: > > drivers/gpu/drm/virtio/virtgpu_ttm.c: In function 'virtio_gpu_init_mem_type': > drivers/gpu/drm/virtio/virtgpu_ttm.c:117:28: warning: > variable 'vgdev' set but not used [-Wunused-but-