[PATCH 4.15 43/60] x86/spectre: Report get_user mitigation for spectre_v1

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams dan.j.willi...@intel.com commit edfbae53dab8348fca778531be9f4855d2ca0360 Reflect the presence of get_user(), __get_user(), and 'syscall' protections in sysfs. The expectation is

[PATCH 4.15 43/60] x86/spectre: Report get_user mitigation for spectre_v1

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams dan.j.willi...@intel.com commit edfbae53dab8348fca778531be9f4855d2ca0360 Reflect the presence of get_user(), __get_user(), and 'syscall' protections in sysfs. The expectation is

[PATCH 4.15 17/60] x86/speculation: Simplify indirect_branch_prediction_barrier()

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Borislav Petkov b...@suse.de commit 64e16720ea0879f8ab4547e3b9758936d483909b Make it all a function which does the WRMSR instead of having a hairy inline asm. [dwmw2: export it, fix

[PATCH 4.15 17/60] x86/speculation: Simplify indirect_branch_prediction_barrier()

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Borislav Petkov b...@suse.de commit 64e16720ea0879f8ab4547e3b9758936d483909b Make it all a function which does the WRMSR instead of having a hairy inline asm. [dwmw2: export it, fix

[PATCH 4.15 44/60] x86/spectre: Fix spelling mistake: "vunerable"-> "vulnerable"

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King colin.k...@canonical.com commit e698dcdfcda41efd0984de539767b4cddd235f1e Trivial fix to spelling mistake in pr_err error message text. Signed-off-by: Colin Ian King

[PATCH 4.15 44/60] x86/spectre: Fix spelling mistake: "vunerable"-> "vulnerable"

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King colin.k...@canonical.com commit e698dcdfcda41efd0984de539767b4cddd235f1e Trivial fix to spelling mistake in pr_err error message text. Signed-off-by: Colin Ian King

[PATCH 4.15 45/60] x86/cpuid: Fix up "virtual" IBRS/IBPB/STIBP feature bits on Intel

4.15-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse d...@amazon.co.uk commit 7fcae1118f5fd44a862aa5c3525248e35ee67c3b Despite the fact that all the other code there seems to be doing it, just using set_cpu_cap() in

[RFC 04/12] KVM/VMX: Use the new host mapping API for pi_desc_page

For nested guests the pi_desc_page was mapped to the host kernel using kvm_vcpu_gpa_to_page which assumes that all guest memory is backed by a "struct page". This breaks guests that have their memory outside the kernel control. Switch to the new host mapping API which takes care of this use-case

[RFC 04/12] KVM/VMX: Use the new host mapping API for pi_desc_page

For nested guests the pi_desc_page was mapped to the host kernel using kvm_vcpu_gpa_to_page which assumes that all guest memory is backed by a "struct page". This breaks guests that have their memory outside the kernel control. Switch to the new host mapping API which takes care of this use-case

[PATCH 4.15 45/60] x86/cpuid: Fix up "virtual" IBRS/IBPB/STIBP feature bits on Intel

4.15-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse d...@amazon.co.uk commit 7fcae1118f5fd44a862aa5c3525248e35ee67c3b Despite the fact that all the other code there seems to be doing it, just using set_cpu_cap() in

[RFC 01/12] KVM: Introduce helper functions to map/unmap guest memory

Introduce helper functions to map and unmap guest memory into host kernel memory. These helper functions support mapping guest memory both that are managed by the host kernel (i.e. have a "struct page") and the ones that are not managed by the kernel (i.e. does not have a "struct page"). Cc:

[RFC 01/12] KVM: Introduce helper functions to map/unmap guest memory

Introduce helper functions to map and unmap guest memory into host kernel memory. These helper functions support mapping guest memory both that are managed by the host kernel (i.e. have a "struct page") and the ones that are not managed by the kernel (i.e. does not have a "struct page"). Cc:

[RFC 06/12] KVM/VMX: Use the new host mapping API for handle_vmptrld

Cc: Paolo Bonzini Cc: Radim Krčmář Cc: k...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: KarimAllah Ahmed --- arch/x86/kvm/vmx.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git

[RFC 06/12] KVM/VMX: Use the new host mapping API for handle_vmptrld

Cc: Paolo Bonzini Cc: Radim Krčmář Cc: k...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: KarimAllah Ahmed --- arch/x86/kvm/vmx.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c index

[RFC 08/12] KVM/VMX: Use the new host mapping API for mapping nested PML

For nested guests the PML page was mapped to the host kernel using kvm_vcpu_gpa_to_page which assumes that all guest memory is backed by a "struct page". This breaks guests that have their memory outside the kernel control. Switch to the new host mapping API which takes care of this use-case as

[RFC 08/12] KVM/VMX: Use the new host mapping API for mapping nested PML

For nested guests the PML page was mapped to the host kernel using kvm_vcpu_gpa_to_page which assumes that all guest memory is backed by a "struct page". This breaks guests that have their memory outside the kernel control. Switch to the new host mapping API which takes care of this use-case as

[RFC 05/12] KVM/VMX: Use the new host mapping API for mapping nested vmptr

For nested guests the vmptr was mapped to the host kernel using kvm_vcpu_gpa_to_page which assumes that all guest memory is backed by a "struct page". This breaks guests that have their memory outside the kernel control. Switch to the new host mapping API which takes care of this use-case as

[RFC 12/12] KVM/VMX: Remove kvm_vcpu_gpa_to_page as it is now unused

Cc: Paolo Bonzini Cc: Radim Krčmář Cc: k...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: KarimAllah Ahmed --- include/linux/kvm_host.h | 6 -- 1 file changed, 6 deletions(-) diff --git

[RFC 12/12] KVM/VMX: Remove kvm_vcpu_gpa_to_page as it is now unused

Cc: Paolo Bonzini Cc: Radim Krčmář Cc: k...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: KarimAllah Ahmed --- include/linux/kvm_host.h | 6 -- 1 file changed, 6 deletions(-) diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h index 45d2854..44db14a 100644

[RFC 05/12] KVM/VMX: Use the new host mapping API for mapping nested vmptr

For nested guests the vmptr was mapped to the host kernel using kvm_vcpu_gpa_to_page which assumes that all guest memory is backed by a "struct page". This breaks guests that have their memory outside the kernel control. Switch to the new host mapping API which takes care of this use-case as

[RFC 02/12] KVM/VMX: Use the new host mapping API for apic_access_page

For nested guests the apic_access_page was mapped to the host kernel using kvm_vcpu_gpa_to_page which assumes that all guest memory is backed by a "struct page". This breaks guests that have their memory outside the kernel control. Switch to the new host mapping API which takes care of this

[RFC 02/12] KVM/VMX: Use the new host mapping API for apic_access_page

For nested guests the apic_access_page was mapped to the host kernel using kvm_vcpu_gpa_to_page which assumes that all guest memory is backed by a "struct page". This breaks guests that have their memory outside the kernel control. Switch to the new host mapping API which takes care of this

[RFC 00/12] KVM/X86: Introduce a new guest mapping API

Guest memory can either be directly managed by the kernel (i.e. have a "struct page") or they can simply live outside kernel control (i.e. do not have a "struct page"). KVM mostly support these two modes, except in a few places where the code seems to assume that guest memory must have a "struct

[RFC 10/12] KVM/VMX: Use the new host mapping API for synic_clear_sint_msg_pending

Cc: Paolo Bonzini Cc: Radim Krčmář Cc: k...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: KarimAllah Ahmed --- arch/x86/kvm/hyperv.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git

[RFC 00/12] KVM/X86: Introduce a new guest mapping API

Guest memory can either be directly managed by the kernel (i.e. have a "struct page") or they can simply live outside kernel control (i.e. do not have a "struct page"). KVM mostly support these two modes, except in a few places where the code seems to assume that guest memory must have a "struct

[RFC 10/12] KVM/VMX: Use the new host mapping API for synic_clear_sint_msg_pending

Cc: Paolo Bonzini Cc: Radim Krčmář Cc: k...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: KarimAllah Ahmed --- arch/x86/kvm/hyperv.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c index

[RFC 03/12] KVM/VMX: Use the new host mapping API for virtual_apic_page

For nested guests the virtual_apic_page was mapped to the host kernel using kvm_vcpu_gpa_to_page which assumes that all guest memory is backed by a "struct page". This breaks guests that have their memory outside the kernel control. Switch to the new host mapping API which takes care of this

[RFC 03/12] KVM/VMX: Use the new host mapping API for virtual_apic_page

For nested guests the virtual_apic_page was mapped to the host kernel using kvm_vcpu_gpa_to_page which assumes that all guest memory is backed by a "struct page". This breaks guests that have their memory outside the kernel control. Switch to the new host mapping API which takes care of this

[RFC 09/12] KVM/VMX: Use the new host mapping API for cmpxchg_emulated

Cc: Paolo Bonzini Cc: Radim Krčmář Cc: k...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: KarimAllah Ahmed --- arch/x86/kvm/x86.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git

[RFC 09/12] KVM/VMX: Use the new host mapping API for cmpxchg_emulated

Cc: Paolo Bonzini Cc: Radim Krčmář Cc: k...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: KarimAllah Ahmed --- arch/x86/kvm/x86.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index ac38143..db0fd24

[RFC 11/12] KVM/VMX: Use the new host mapping API for synic_deliver_msg

Cc: Paolo Bonzini Cc: Radim Krčmář Cc: k...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: KarimAllah Ahmed --- arch/x86/kvm/hyperv.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git

[RFC 11/12] KVM/VMX: Use the new host mapping API for synic_deliver_msg

Cc: Paolo Bonzini Cc: Radim Krčmář Cc: k...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: KarimAllah Ahmed --- arch/x86/kvm/hyperv.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c index

[RFC 07/12] KVM/VMX: Use the new host mapping API for mapping L12 MSR bitmap

For nested guests the L12 MSR bitmap was mapped to the host kernel using kvm_vcpu_gpa_to_page which assumes that all guest memory is backed by a "struct page". This breaks guests that have their memory outside the kernel control. Switch to the new host mapping API which takes care of this

[RFC 07/12] KVM/VMX: Use the new host mapping API for mapping L12 MSR bitmap

For nested guests the L12 MSR bitmap was mapped to the host kernel using kvm_vcpu_gpa_to_page which assumes that all guest memory is backed by a "struct page". This breaks guests that have their memory outside the kernel control. Switch to the new host mapping API which takes care of this

[PATCH 4.15 21/60] ASoC: pcm512x: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Jesse Chan commit 0cab20cec0b663b7be8e2be5998d5a4113647f86 upstream. This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost:

[PATCH 4.15 21/60] ASoC: pcm512x: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Jesse Chan commit 0cab20cec0b663b7be8e2be5998d5a4113647f86 upstream. This change resolves a new compile-time warning when built as a loadable module: WARNING: modpost: missing

[PATCH 4.15 48/60] KVM: VMX: make MSR bitmaps per-VCPU

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini pbonz...@redhat.com commit 904e14fb7cb96401a7dc803ca2863fd5ba32ffe6 Place the MSR bitmap in struct loaded_vmcs, and update it in place every time the x2apic or APICv state can

[PATCH 4.15 48/60] KVM: VMX: make MSR bitmaps per-VCPU

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini pbonz...@redhat.com commit 904e14fb7cb96401a7dc803ca2863fd5ba32ffe6 Place the MSR bitmap in struct loaded_vmcs, and update it in place every time the x2apic or APICv state can

Re: [PATCH 1/3] x86/entry: Clear extra registers beyond syscall arguments for 64bit kernels

On Mon, Feb 5, 2018 at 1:29 PM, Ingo Molnar wrote: > > * Andy Lutomirski wrote: > >> [...] Clearing R10 is mostly useless in the syscall path because we'll just >> unconditionally reload it in do_syscall_64(). > > AFAICS do_syscall_64() doesn't touch R10 at

Re: [PATCH 1/3] x86/entry: Clear extra registers beyond syscall arguments for 64bit kernels

On Mon, Feb 5, 2018 at 1:29 PM, Ingo Molnar wrote: > > * Andy Lutomirski wrote: > >> [...] Clearing R10 is mostly useless in the syscall path because we'll just >> unconditionally reload it in do_syscall_64(). > > AFAICS do_syscall_64() doesn't touch R10 at all. So how does it reload R10? > > In

[PATCH 4.15 51/60] x86/spectre: Simplify spectre_v2 command line parsing

4.15-stable review patch. If anyone has any objections, please let me know. -- From: KarimAllah Ahmed karah...@amazon.de commit 9005c6834c0ffdfe46afa76656bd9276cca864f6 [dwmw2: Use ARRAY_SIZE] Signed-off-by: KarimAllah Ahmed Signed-off-by: David Woodhouse

[PATCH 4.15 51/60] x86/spectre: Simplify spectre_v2 command line parsing

4.15-stable review patch. If anyone has any objections, please let me know. -- From: KarimAllah Ahmed karah...@amazon.de commit 9005c6834c0ffdfe46afa76656bd9276cca864f6 [dwmw2: Use ARRAY_SIZE] Signed-off-by: KarimAllah Ahmed Signed-off-by: David Woodhouse Signed-off-by:

[PATCH 4.15 52/60] x86/pti: Mark constant arrays as __initconst

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann a...@arndb.de commit 4bf5d56d429cbc96c23d809a08f63cd29e1a702e I'm seeing build failures from the two newly introduced arrays that are marked 'const' and '__initdata', which are

[PATCH 4.15 52/60] x86/pti: Mark constant arrays as __initconst

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann a...@arndb.de commit 4bf5d56d429cbc96c23d809a08f63cd29e1a702e I'm seeing build failures from the two newly introduced arrays that are marked 'const' and '__initdata', which are

[PATCH 4.15 53/60] x86/speculation: Fix typo IBRS_ATT, which should be IBRS_ALL

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Darren Kenny darren.ke...@oracle.com commit af189c95a371b59f493dbe0f50c0a09724868881 Fixes: 117cc7a908c83 ("x86/retpoline: Fill return stack buffer on vmexit") Signed-off-by: Darren Kenny

[PATCH 4.15 53/60] x86/speculation: Fix typo IBRS_ATT, which should be IBRS_ALL

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Darren Kenny darren.ke...@oracle.com commit af189c95a371b59f493dbe0f50c0a09724868881 Fixes: 117cc7a908c83 ("x86/retpoline: Fill return stack buffer on vmexit") Signed-off-by: Darren Kenny

Re: clang warning: implicit conversion in intel_ddi.c:1481

> > We are interested who is we?

Re: clang warning: implicit conversion in intel_ddi.c:1481

> > We are interested who is we?

[PATCH 4.15 57/60] KVM/VMX: Allow direct access to MSR_IA32_SPEC_CTRL

4.15-stable review patch. If anyone has any objections, please let me know. -- From: KarimAllah Ahmed karah...@amazon.de commit d28b387fb74da95d69d2615732f50cceb38e9a4d [ Based on a patch from Ashok Raj ] Add direct access to MSR_IA32_SPEC_CTRL for

[PATCH 4.15 58/60] KVM/SVM: Allow direct access to MSR_IA32_SPEC_CTRL

4.15-stable review patch. If anyone has any objections, please let me know. -- From: KarimAllah Ahmed karah...@amazon.de commit b2ac58f90540e39324e7a29a7ad471407ae0bf48 [ Based on a patch from Paolo Bonzini ] ... basically doing exactly what we do for

[PATCH 4.15 57/60] KVM/VMX: Allow direct access to MSR_IA32_SPEC_CTRL

4.15-stable review patch. If anyone has any objections, please let me know. -- From: KarimAllah Ahmed karah...@amazon.de commit d28b387fb74da95d69d2615732f50cceb38e9a4d [ Based on a patch from Ashok Raj ] Add direct access to MSR_IA32_SPEC_CTRL for guests. This is needed for

[PATCH 4.15 58/60] KVM/SVM: Allow direct access to MSR_IA32_SPEC_CTRL

4.15-stable review patch. If anyone has any objections, please let me know. -- From: KarimAllah Ahmed karah...@amazon.de commit b2ac58f90540e39324e7a29a7ad471407ae0bf48 [ Based on a patch from Paolo Bonzini ] ... basically doing exactly what we do for VMX: - Passthrough

[PATCH 4.15 59/60] serial: core: mark port as initialized after successful IRQ change

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 44117a1d1732c513875d5a163f10d9adbe866c08 upstream. setserial changes the IRQ via uart_set_info(). It invokes uart_shutdown() which free

[PATCH 4.15 59/60] serial: core: mark port as initialized after successful IRQ change

4.15-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 44117a1d1732c513875d5a163f10d9adbe866c08 upstream. setserial changes the IRQ via uart_set_info(). It invokes uart_shutdown() which free the current used IRQ

[PATCH 4.15 50/60] x86/retpoline: Avoid retpolines for built-in __init functions

4.15-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse d...@amazon.co.uk commit 66f793099a636862a71c59d4a6ba91387b155e0c There's no point in building init code with retpolines, since it runs before any potentially hostile userspace

[PATCH 4.15 50/60] x86/retpoline: Avoid retpolines for built-in __init functions

4.15-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse d...@amazon.co.uk commit 66f793099a636862a71c59d4a6ba91387b155e0c There's no point in building init code with retpolines, since it runs before any potentially hostile userspace

[PATCH 3.18 01/36] Input: do not emit unneeded EV_SYN when suspending

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Torokhov commit 00159f19a5057cb779146afce1cceede692af346 upstream. Do not emit EV_SYN/SYN_REPORT on suspend if there were no keys that are still pressed as

[PATCH 3.18 01/36] Input: do not emit unneeded EV_SYN when suspending

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Torokhov commit 00159f19a5057cb779146afce1cceede692af346 upstream. Do not emit EV_SYN/SYN_REPORT on suspend if there were no keys that are still pressed as we are suspending the device

Re: [PATCH v5 3/3] KVM: nVMX: Fix mmu context after VMLAUNCH/VMRESUME failure

I realize now that this fix isn't quite right, since it loads vmcs12->host_cr3 rather than reverting to the CR3 that was loaded at the time of VMLAUNCH/VMRESUME. In the case of VMfailValid(VM entry with invalid VMX-control field(s)), none of the VMCS12 host state fields should be loaded. See the

Re: [PATCH v5 3/3] KVM: nVMX: Fix mmu context after VMLAUNCH/VMRESUME failure

I realize now that this fix isn't quite right, since it loads vmcs12->host_cr3 rather than reverting to the CR3 that was loaded at the time of VMLAUNCH/VMRESUME. In the case of VMfailValid(VM entry with invalid VMX-control field(s)), none of the VMCS12 host state fields should be loaded. See the

[PATCH 3.18 13/36] mac80211: fix the update of path metric for RANN frame

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Chun-Yeow Yeoh [ Upstream commit fbbdad5edf0bb59786a51b94a9d006bc8c2da9a2 ] The previous path metric update from RANN frame has not considered the own link metric

[PATCH 3.18 13/36] mac80211: fix the update of path metric for RANN frame

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Chun-Yeow Yeoh [ Upstream commit fbbdad5edf0bb59786a51b94a9d006bc8c2da9a2 ] The previous path metric update from RANN frame has not considered the own link metric toward the transmitting

Re: [PATCH] libnvdimm: remove redundant assignment to pointer 'dev'

On Mon, Feb 5, 2018 at 10:20 AM, Ross Zwisler wrote: > On Mon, Feb 05, 2018 at 02:08:52PM +, Colin King wrote: >> From: Colin Ian King >> >> Pointer dev is being assigned a value that is never read, it is being >> re-assigned the same

Re: [PATCH] libnvdimm: remove redundant assignment to pointer 'dev'

On Mon, Feb 5, 2018 at 10:20 AM, Ross Zwisler wrote: > On Mon, Feb 05, 2018 at 02:08:52PM +, Colin King wrote: >> From: Colin Ian King >> >> Pointer dev is being assigned a value that is never read, it is being >> re-assigned the same value later on, hence the initialization is redundant >>

[PATCH 3.18 17/36] nfsd: check for use of the closed special stateid

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andrew Elble [ Upstream commit ae254dac721d44c0bfebe2795df87459e2e88219 ] Prevent the use of the closed (invalid) special stateid by clients. Signed-off-by: Andrew Elble

[PATCH 3.18 15/36] xen-netfront: remove warning when unloading module

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eduardo Otubo [ Upstream commit 5b5971df3bc2775107ddad164018a8a8db633b81 ] v2: * Replace busy wait with wait_event()/wake_up_all() * Cannot garantee that at the time

[PATCH 3.18 17/36] nfsd: check for use of the closed special stateid

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andrew Elble [ Upstream commit ae254dac721d44c0bfebe2795df87459e2e88219 ] Prevent the use of the closed (invalid) special stateid by clients. Signed-off-by: Andrew Elble Signed-off-by: J.

[PATCH 3.18 15/36] xen-netfront: remove warning when unloading module

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eduardo Otubo [ Upstream commit 5b5971df3bc2775107ddad164018a8a8db633b81 ] v2: * Replace busy wait with wait_event()/wake_up_all() * Cannot garantee that at the time xennet_remove is

[PATCH 3.18 16/36] nfsd: CLOSE SHOULD return the invalid special stateid for NFSv4.x (x>0)

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust [ Upstream commit fb500a7cfee7f2f447d2bbf30cb59629feab6ac1 ] Signed-off-by: Trond Myklebust Signed-off-by:

[PATCH 3.18 16/36] nfsd: CLOSE SHOULD return the invalid special stateid for NFSv4.x (x>0)

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust [ Upstream commit fb500a7cfee7f2f447d2bbf30cb59629feab6ac1 ] Signed-off-by: Trond Myklebust Signed-off-by: J. Bruce Fields Signed-off-by: Sasha Levin Signed-off-by: Greg

[PATCH 3.18 18/36] hwmon: (pmbus) Use 64bit math for DIRECT format values

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Robert Lippert [ Upstream commit bd467e4eababe4c04272c1e646f066db02734c79 ] Power values in the 100s of watt range can easily blow past 32bit math limits when processing

[PATCH 3.18 18/36] hwmon: (pmbus) Use 64bit math for DIRECT format values

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Robert Lippert [ Upstream commit bd467e4eababe4c04272c1e646f066db02734c79 ] Power values in the 100s of watt range can easily blow past 32bit math limits when processing everything in

Re: [GIT PULL REQUEST] watchdog - v4.16 merge window

On Mon, Feb 05, 2018 at 09:50:54AM -0800, Linus Torvalds wrote: > On Mon, Feb 5, 2018 at 2:20 AM, Wim Van Sebroeck wrote: > > > > git://www.linux-watchdog.org/linux-watchdog.git > > Hmm. I really want to know why I should pull this. You have the > shortlog and the diffstat, but

Re: [GIT PULL REQUEST] watchdog - v4.16 merge window

On Mon, Feb 05, 2018 at 09:50:54AM -0800, Linus Torvalds wrote: > On Mon, Feb 5, 2018 at 2:20 AM, Wim Van Sebroeck wrote: > > > > git://www.linux-watchdog.org/linux-watchdog.git > > Hmm. I really want to know why I should pull this. You have the > shortlog and the diffstat, but you don't

[PATCH 3.18 19/36] net: ethernet: xilinx: Mark XILINX_LL_TEMAC broken on 64-bit

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven [ Upstream commit 15bfe05c8d6386f1a90e9340d15336e85e32aad6 ] On 64-bit (e.g. powerpc64/allmodconfig):

[PATCH 3.18 19/36] net: ethernet: xilinx: Mark XILINX_LL_TEMAC broken on 64-bit

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven [ Upstream commit 15bfe05c8d6386f1a90e9340d15336e85e32aad6 ] On 64-bit (e.g. powerpc64/allmodconfig): drivers/net/ethernet/xilinx/ll_temac_main.c: In function

[PATCH 3.18 02/36] um: link vmlinux with -no-pie

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Meyer commit 883354afbc109c57f925ccc19840055193da0cc0 upstream. Debian's gcc defaults to pie. The global Makefile already defines the -fno-pie option. Link UML

[PATCH 3.18 02/36] um: link vmlinux with -no-pie

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Meyer commit 883354afbc109c57f925ccc19840055193da0cc0 upstream. Debian's gcc defaults to pie. The global Makefile already defines the -fno-pie option. Link UML dynamic kernel image

[PATCH 3.18 21/36] scsi: ufs: ufshcd: fix potential NULL pointer dereference in ufshcd_config_vreg

3.18-stable review patch. If anyone has any objections, please let me know. -- From: "Gustavo A. R. Silva" [ Upstream commit 727535903bea924c4f73abb202c4b3e85fff0ca4 ] _vreg_ is being dereferenced before it is null checked, hence there is a potential

[PATCH 3.18 21/36] scsi: ufs: ufshcd: fix potential NULL pointer dereference in ufshcd_config_vreg

3.18-stable review patch. If anyone has any objections, please let me know. -- From: "Gustavo A. R. Silva" [ Upstream commit 727535903bea924c4f73abb202c4b3e85fff0ca4 ] _vreg_ is being dereferenced before it is null checked, hence there is a potential null pointer

[PATCH 3.18 22/36] media: usbtv: add a new usbid

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Icenowy Zheng [ Upstream commit 04226916d2360f56d57ad00bc48d2d1854d1e0b0 ] A new usbid of UTV007 is found in a newly bought device. The usbid is 1f71:3301. The ID on the

[PATCH 3.18 22/36] media: usbtv: add a new usbid

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Icenowy Zheng [ Upstream commit 04226916d2360f56d57ad00bc48d2d1854d1e0b0 ] A new usbid of UTV007 is found in a newly bought device. The usbid is 1f71:3301. The ID on the chip is: UTV007

[PATCH 3.18 20/36] quota: Check for register_shrinker() failure.

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tetsuo Handa [ Upstream commit 88bc0ede8d35edc969350852894dc864a2dc1859 ] register_shrinker() might return -ENOMEM error since Linux 3.12. Call panic() as

[PATCH 3.18 20/36] quota: Check for register_shrinker() failure.

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tetsuo Handa [ Upstream commit 88bc0ede8d35edc969350852894dc864a2dc1859 ] register_shrinker() might return -ENOMEM error since Linux 3.12. Call panic() as with other failure checks in this

[PATCH 3.18 23/36] usb: gadget: dont dereference g until after it has been null checked

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit b2fc059fa549fe6881d4c1f8d698b0f50bcd16ec ] Avoid dereferencing pointer g until after g has been sanity null checked; move the

[PATCH 3.18 23/36] usb: gadget: dont dereference g until after it has been null checked

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit b2fc059fa549fe6881d4c1f8d698b0f50bcd16ec ] Avoid dereferencing pointer g until after g has been sanity null checked; move the assignment of cdev much later

[PATCH 3.18 24/36] staging: rtl8188eu: Fix incorrect response to SIOCGIWESSID

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Larry Finger [ Upstream commit b77992d2df9e47144354d1b25328b180afa33442 ] When not associated with an AP, wifi device drivers should respond to the SIOCGIWESSID

RE: [PATCH] arc: dts: use 'atmel' as manufacturer for at24 in axs10x_mb

Hi Bartosz, all, > -Original Message- > From: Bartosz Golaszewski [mailto:b...@bgdev.pl] > Sent: Thursday, January 25, 2018 12:40 AM > To: Rob Herring ; Mark Rutland ; > Russell King ; Alexey > Brodkin

[PATCH 3.18 24/36] staging: rtl8188eu: Fix incorrect response to SIOCGIWESSID

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Larry Finger [ Upstream commit b77992d2df9e47144354d1b25328b180afa33442 ] When not associated with an AP, wifi device drivers should respond to the SIOCGIWESSID ioctl with a zero-length

RE: [PATCH] arc: dts: use 'atmel' as manufacturer for at24 in axs10x_mb

Hi Bartosz, all, > -Original Message- > From: Bartosz Golaszewski [mailto:b...@bgdev.pl] > Sent: Thursday, January 25, 2018 12:40 AM > To: Rob Herring ; Mark Rutland ; > Russell King ; Alexey > Brodkin ; Vineet Gupta > > Cc: devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; >

[PATCH 3.18 27/36] CDC-ACM: apply quirk for card reader

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit df1cc78a52491f71d8170d513d0f6f114faa1bda upstream. This devices drops random bytes from messages if you talk to it too fast. Signed-off-by: Oliver

[PATCH 3.18 27/36] CDC-ACM: apply quirk for card reader

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit df1cc78a52491f71d8170d513d0f6f114faa1bda upstream. This devices drops random bytes from messages if you talk to it too fast. Signed-off-by: Oliver Neukum Signed-off-by:

[PATCH 3.18 28/36] USB: serial: io_edgeport: fix possible sleep-in-atomic

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jia-Ju Bai commit c7b8f77872c73f69a16528a9eb87afefcccdc18b upstream. According to drivers/usb/serial/io_edgeport.c, the driver may sleep under a spinlock. The function

[PATCH 3.18 26/36] USB: cdc-acm: Do not log urb submission errors on disconnect

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit f0386c083c2ce85284dc0b419d7b89c8e567c09f upstream. When disconnected sometimes the cdc-acm driver logs errors like these: [20278.039417] cdc_acm

[PATCH 3.18 28/36] USB: serial: io_edgeport: fix possible sleep-in-atomic

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jia-Ju Bai commit c7b8f77872c73f69a16528a9eb87afefcccdc18b upstream. According to drivers/usb/serial/io_edgeport.c, the driver may sleep under a spinlock. The function call path is:

[PATCH 3.18 26/36] USB: cdc-acm: Do not log urb submission errors on disconnect

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit f0386c083c2ce85284dc0b419d7b89c8e567c09f upstream. When disconnected sometimes the cdc-acm driver logs errors like these: [20278.039417] cdc_acm 2-2:2.1: urb 9 failed

[PATCH 3.18 03/36] um: Stop abusing __KERNEL__

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Richard Weinberger commit 298e20ba8c197e8d429a6c8671550c41c7919033 upstream. Currently UML is abusing __KERNEL__ to distinguish between kernel and host code (os-Linux). It is

[PATCH 3.18 29/36] usbip: prevent bind loops on devices attached to vhci_hcd

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan commit ef54cf0c600fb8f5737fb001a9e357edda1a1de8 upstream. usbip host binds to devices attached to vhci_hcd on the same server when user does attach over

[PATCH 3.18 03/36] um: Stop abusing __KERNEL__

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Richard Weinberger commit 298e20ba8c197e8d429a6c8671550c41c7919033 upstream. Currently UML is abusing __KERNEL__ to distinguish between kernel and host code (os-Linux). It is better to use a

[PATCH 3.18 29/36] usbip: prevent bind loops on devices attached to vhci_hcd

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan commit ef54cf0c600fb8f5737fb001a9e357edda1a1de8 upstream. usbip host binds to devices attached to vhci_hcd on the same server when user does attach over localhost or specifies the

<    4   5   6   7   8   9   10   11   12   13   >