[PATCH 4.9 45/96] x86/microcode/intel: Extend BDW late-loading with a revision check

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jia Zhang commit b94b7373317164402ff7728d10f7023127a02b60 upstream. Instead of blacklisting all model 79 CPUs when attempting a late microcode loading, limit that only to CPUs with microcode re

Re: [PATCH 3/5] x86/ibrs: Add direct access support for MSR_IA32_SPEC_CTRL

On Fri, Jan 12, 2018 at 10:09:08AM +, David Woodhouse wrote: > static_cpu_has() + asm-goto is NOT SUFFICIENT. > > It's still *possible* for a missed optimisation in GCC to still leave > us with a conditional branch around the wrmsr, letting the CPU > speculate around it too. OK, so GCC would

[PATCH 4.9 46/96] KVM: x86: Add memory barrier on vmcs field lookup

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andrew Honig commit 75f139aaf896d6fdeec2e468ddfa4b2fe469bf40 upstream. This adds a memory barrier when performing a lookup into the vmcs_field_to_offset_table. This is related to CVE-2017-5753

[PATCH 4.9 48/96] kaiser: Set _PAGE_NX only if supported

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Lepton Wu This finally resolve crash if loaded under qemu + haxm. Haitao Shan pointed out that the reason of that crash is that NX bit get set for page tables. It seems we missed checking if _PA

[PATCH 4.9 50/96] target: Avoid early CMD_T_PRE_EXECUTE failures during ABORT_TASK

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Bellinger commit 1c21a48055a67ceb693e9c2587824a8de60a217c upstream. This patch fixes bug where early se_cmd exceptions that occur before backend execution can result in use-after-free

[PATCH 4.9 52/96] bpf: refactor fixup_bpf_calls()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexei Starovoitov commit 79741b3bdec01a8628368fbcfccc7d189ed606cb upstream. reduce indent and make it iterate over instructions similar to convert_ctx_accesses(). Also convert hard BUG_ON into

Re: INFO: task hung in filemap_fault

On Mon, Jan 15, 2018 at 11:44 AM, Tetsuo Handa wrote: >> >>We can't simply drop info from there. Do you propose to add >> >> another attached file that contains the same info in a different >> >> format? What is the exact format you are proposing? >> > >> > Plain C program which can be com

Re: [PATCH v6 1/5] kaslr: add kaslr_mem=nn[KMG]@ss[KMG] to specify extracting memory

On Mon, Jan 15, 2018 at 08:40:12PM +0800, Chao Fan wrote: >In current code, kaslr only has a method to avoid some memory regions, >but no method to specify the regions for kaslr to extract. So kaslr >may choose the wrong position sometimes, which will cause some other >features fail. > >Here is a p

[PATCH 4.9 27/96] sr9700: use skb_cow_head() to deal with cloned skbs

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit d532c1082f68176363ed766d09bf187616e282fe upstream. We need to ensure there is enough headroom to push extra header, but we also need to check if we are allowed to change hea

Re: [PATCH] drm/dsi: Fix improper use of mipi_dsi_device_transfer() return value

Hi Andrzej, On 01/15/2018 10:12 AM, Andrzej Hajda wrote: > On 12.01.2018 15:48, Philippe Cornu wrote: >> The function mipi_dsi_device_transfer() returns the number of transmitted >> or received bytes on success or a negative error code on failure. >> >> The functions mipi_dsi_shutdown_peripheral()

[PATCH 4.9 54/96] bpf, array: fix overflow in max_entries and undefined behavior in index_mask

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann commit bbeb6e4323dad9b5e0ee9f60c223dd532e2403b1 upstream. syzkaller tried to alloc a map with 0xfffd entries out of a userns, and thus unprivileged. With the recently added

[PATCH 4.9 57/96] usb: misc: usb3503: make sure reset is low for at least 100us

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Agner commit b8626f1dc29d3eee444bfaa92146ec7b291ef41c upstream. When using a GPIO which is high by default, and initialize the driver in USB Hub mode, initialization fails with: [ 111

Re: [PATCH 1/3] mfd/omap-usb-tll: Delete two error messages for a failed memory allocation in usbtll_omap_probe()

Marcus, On Mon, Jan 15, 2018 at 02:15:11PM +0100, SF Markus Elfring wrote: > Omit extra messages for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus Elfring > --- > drivers/mfd/omap-usb-tll.c | 5 + > 1 f

[PATCH 4.9 60/96] usbip: fix vudc_rx: harden CMD_SUBMIT path to handle malicious input

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan commit b78d830f0049ef1966dc1e0ebd1ec2a594e2cf25 upstream. Harden CMD_SUBMIT path to handle malicious input that could trigger large memory allocations. Add checks to validate transfe

[PATCH 4.9 59/96] usbip: remove kernel addresses from usb device and urb debug msgs

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan commit e1346fd87c71a1f61de1fe476ec8df1425ac931c upstream. usbip_dump_usb_device() and usbip_dump_urb() print kernel addresses. Remove kernel addresses from usb device and urb debug m

[PATCH 4.9 61/96] usbip: vudc_tx: fix v_send_ret_submit() vulnerability to null xfer buffer

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan commit 5fd77a3a0e408c23ab4002a57db980e46bc16e72 upstream. v_send_ret_submit() handles urb with a null transfer_buffer, when it replays a packet with potential malicious data that cou

[PATCH 4.9 28/96] smsc75xx: use skb_cow_head() to deal with cloned skbs

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit b7c6d2675899cfff0180412c63fc9cbd5bacdb4d upstream. We need to ensure there is enough headroom to push extra header, but we also need to check if we are allowed to change hea

[PATCH 4.9 30/96] xhci: Fix ring leak in failure path of xhci_alloc_virt_device()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings This is a stable-only fix for the backport of commit 5d9b70f7d52e ("xhci: Don't add a virt_dev to the devs array before it's fully allocated"). In branches that predate commit c56

[PATCH 4.9 32/96] ip6_tunnel: disable dst caching if tunnel is dual-stack

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eli Cooper [ Upstream commit 23263ec86a5f44312d2899323872468752324107 ] When an ip6_tunnel is in mode 'any', where the transport layer protocol can be either 4 or 41, dst_cache must be disable

[PATCH 4.9 24/96] x86/acpi: Reduce code duplication in mp_override_legacy_irq()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vikas C Sajjan commit 4ee2ec1b122599f7b10c849fa7915cebb37b7edb upstream. The new function mp_register_ioapic_irq() is a subset of the code in mp_override_legacy_irq(). Replace the code duplica

[PATCH net-next v6 0/2] net: thunderx: add support for PTP clock

This series adds support for IEEE 1588 Precision Time Protocol to Cavium ethernet driver. The first patch adds support for the Precision Time Protocol Clocks and Timestamping coprocessor (PTP) found on Cavium processors. It registers a new PTP clock in the PTP core and provides functions to use th

Re: LKML admins (syzbot emails are not delivered)

On Mon, Jan 15, 2018 at 2:08 PM, Pavel Machek wrote: > On Mon 2018-01-15 11:08:12, Dmitry Vyukov wrote: >> On Thu, Jan 4, 2018 at 12:18 PM, Pavel Machek wrote: >> > On Thu 2018-01-04 12:09:26, Dmitry Vyukov wrote: >> >> On Thu, Jan 4, 2018 at 10:56 AM, Pavel Machek wrote: >> >> >> On Thu, 2018-0

[PATCH 4.9 72/96] x86/cpu: Merge bugs.c and bugs_64.c

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Borislav Petkov commit 62a67e123e058a67db58bc6a14354dd037bafd0a upstream. Should be easier when following boot paths. It probably is a left over from the x86 unification eons ago. No functiona

[PATCH 4.9 33/96] net: core: fix module type in sock_diag_bind

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andrii Vladyka [ Upstream commit b8fd0823e0770c2d5fdbd865bccf0d5e058e5287 ] Use AF_INET6 instead of AF_INET in IPv6-related code path Signed-off-by: Andrii Vladyka Signed-off-by: David S. Mi

Re: [PATCH 4.14 053/118] Revert "Revert "xfrm: Fix stack-out-of-bounds read in xfrm_state_find.""

On Mon, Jan 15, 2018 at 02:23:29PM +0100, Steffen Klassert wrote: > On Mon, Jan 15, 2018 at 01:34:40PM +0100, Greg Kroah-Hartman wrote: > > 4.14-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: "David S. Miller" > > > > > > This r

[PATCH 4.9 74/96] x86/cpu: Implement CPU vulnerabilites sysfs functions

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 61dc0f555b5c761cdafb0ba5bd41ecf22d68a4c4 upstream. Implement the CPU vulnerabilty show functions for meltdown, spectre_v1 and spectre_v2. Signed-off-by: Thomas Gleixner

[PATCH net-next v6 2/2] net: thunderx: add timestamping support

From: Sunil Goutham This adds timestamping support for both receive and transmit paths. On the receive side no filters are supported i.e either all pkts will get a timestamp appended infront of the packet or none. On the transmit side HW doesn't support timestamp insertion but only generates a se

[PATCH 4.9 76/96] x86/cpu/AMD: Use LFENCE_RDTSC in preference to MFENCE_RDTSC

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tom Lendacky commit 9c6a73c75864ad9fa49e5fa6513e4c4071c0e29f upstream. With LFENCE now a serializing instruction, use LFENCE_RDTSC in preference to MFENCE_RDTSC. However, since the kernel coul

Re: [Suspected-Phishing]Re: [PATCH V3 1/2] nvme: split resetting state into reset_prepate and resetting

On 1/15/2018 3:28 PM, Max Gurtovoy wrote: On 1/14/2018 11:48 AM, Sagi Grimberg wrote: Currently, the ctrl->state will be changed to NVME_CTRL_RESETTING before queue the reset work. This is not so strict. There could be a big gap before the reset_work callback is invoked. In addition, there

[PATCH 4.9 73/96] sysfs/cpu: Add vulnerability folder

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 87590ce6e373d1a5401f6539f0c59ef92dd924a9 upstream. As the meltdown/spectre problem affects several CPU architectures, it makes sense to have common way to express whether

[PATCH 4.9 75/96] x86/cpu/AMD: Make LFENCE a serializing instruction

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tom Lendacky commit e4d0e84e490790798691aaa0f2e598637f1867ec upstream. To aid in speculation control, make LFENCE a serializing instruction since it has less overhead than MFENCE. This is done

[PATCH 4.9 78/96] x86/alternatives: Fix optimize_nops() checking

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Borislav Petkov commit 612e8e9350fd19cae6900cf36ea0c6892d1a0dca upstream. The alternatives code checks only the first byte whether it is a NOP, but with NOPs in front of the payload and having

[PATCH 4.9 80/96] x86/mm/32: Move setup_clear_cpu_cap(X86_FEATURE_PCID) earlier

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit b8b7abaed7a49b350f8ba659ddc264b04931d581 upstream. Otherwise we might have the PCID feature bit set during cpu_init(). This is just for robustness. I haven't seen any a

[PATCH 4.9 82/96] objtool: Detect jumps to retpoline thunks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Josh Poimboeuf commit 39b735332cb8b33a27c28592d969e4016c86c3ea upstream. A direct jump to a retpoline thunk is really an indirect jump in disguise. Change the objtool instruction type accordin

[PATCH 4.9 84/96] x86/asm: Use register variable to get stack pointer value

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit 196bd485ee4f03ce4c690bfcf38138abfcd0a4bc upstream. Currently we use current_stack_pointer() function to get the value of the stack pointer register. Since commit: f5ca

[PATCH 1/4] crypto: ccp: Fix sparse, use plain integer as NULL pointer

Fix sparse warning: Using plain integer as NULL pointer. Replaces assignment of 0 to pointer with NULL assignment. Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Borislav Petkov Cc: Herbert Xu Cc: Gary Hook Cc: Tom Lendacky Cc: linux-cry...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-o

[PATCH 3/4] include: psp-sev: Capitalize invalid length enum

Commit 1d57b17c60ff ("crypto: ccp: Define SEV userspace ioctl and command id") added the invalid length enum but we missed capitalizing it. Fixes: 1d57b17c60ff (crypto: ccp: Define SEV userspace ioctl ...) Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Borislav Petkov Cc: Tom Lendacky CC: Gary R Hoo

[PATCH 4/4] KVM: SVM: Fix SEV LAUNCH_SECRET command

The SEV LAUNCH_SECRET command fails with error code 'invalid param' because we missed filling the guest and header system physical address while issuing the command. Fixes: 9f5b5b950aa9 (KVM: SVM: Add support for SEV LAUNCH_SECRET command) Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Borislav Petkov

[PATCH 2/4] KVM: SVM: Fix sparse: incorrect type in argument 1 (different base types)

Fix sparse: incorrect type in argument 1 (different base types). Typecast the userspace address argument. Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Borislav Petkov Cc: Tom Lendacky Cc: linux-kernel@vger.kernel.org Cc: Joerg Roedel Signed-off-by: Brijesh Singh --- arch/x86/kvm/svm.c | 4 +++-

[PATCH 0/4] KVM: SVM: kbuild test robot warning fixes

The patch series fixes the warnings reported by kbuild test robot after SEV patches. Additionally, during testing I found that LAUNCH_SECRET command was broken and patch series contains the fix for it. The patch series applies on kvm/queue branch. Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Boris

Re: arch/x86/kvm/x86.c:7111:23: warning: this statement may fall through [-Wimplicit-fallthrough=]

On 15/01/2018 13:34, David Binderman wrote: > Hello there, > > > Source code is > > >     switch(vcpu->arch.mp_state) { >     case KVM_MP_STATE_HALTED: >     vcpu->arch.pv.pv_unhalted = false; >     vcpu->arch.mp_state = >     KVM_MP_STATE_RUNNABLE; >     case KVM_MP_STATE_RUNNA

[PATCH 4.9 86/96] x86/spectre: Add boot time option to select Spectre v2 mitigation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit da285121560e769cc31797bba6422eea71d473e0 upstream. Add a spectre_v2= option to select the mitigation used for the indirect branch speculation vulnerability. Currently, t

[PATCH 4.9 87/96] x86/retpoline/crypto: Convert crypto assembler indirect jumps

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit 9697fa39efd3fc3692f2949d4045f393ec58450b upstream. Convert all indirect jumps in crypto assembler code to use non-speculative sequences when CONFIG_RETPOLINE is enabled.

[PATCH 4.9 89/96] x86/retpoline/ftrace: Convert ftrace assembler indirect jumps

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit 9351803bd803cdbeb9b5a7850b7b6f464806e3db upstream. Convert all indirect jumps in ftrace assembler code to use non-speculative sequences when CONFIG_RETPOLINE is enabled.

[PATCH 4.9 91/96] x86/retpoline/xen: Convert Xen hypercall indirect jumps

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit ea08816d5b185ab3d09e95e393f265af54560350 upstream. Convert indirect call in Xen hypercall to use non-speculative sequence, when CONFIG_RETPOLINE is enabled. Signed-off-b

[PATCH 4.9 90/96] x86/retpoline/hyperv: Convert assembler indirect jumps

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit e70e5892b28c18f517f29ab6e83bd57705104b31 upstream. Convert all indirect jumps in hyperv inline asm code to use non-speculative sequences when CONFIG_RETPOLINE is enabled.

[PATCH] powerpc/pseries: include linux/types.h in asm/hvcall.h

Commit 6e032b350cd1 ("powerpc/powernv: Check device-tree for RFI flush settings") uses u64 in asm/hvcall.h without including linux/types.h This breaks hvcall.h users that do not include the header themselves. Fixes: 6e032b350cd1 ("powerpc/powernv: Check device-tree for RFI flush settings") S

Re: [PATCH v6 02/36] openrisc: add ioremap_nocache declaration before include asm-generic/io.h and sync ioremap prototype with it.

2018-01-15 21:07 GMT+08:00 Stafford Horne : > On Mon, Jan 15, 2018 at 01:53:10PM +0800, Greentime Hu wrote: >> From: Greentime Hu >> >> It will be built failed if commit id: d25ea659 is selected. This patch can >> fix this >> build error. > > Hello, > > As I mentioned last time, can you you chang

[PATCH 4.9 65/96] e1000e: Fix e1000_check_for_copper_link_ich8lan return value.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Poirier commit 4110e02eb45ea447ec6f5459c9934de0a273fb91 upstream. e1000e_check_for_copper_link() and e1000_check_for_copper_link_ich8lan() are the two functions that may be assigned to

[PATCH 4.9 93/96] x86/retpoline/irq32: Convert assembler indirect jumps

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andi Kleen commit 7614e913db1f40fff819b36216484dc3808995d4 upstream. Convert all indirect jumps in 32bit irq inline asm code to use non speculative sequences. Signed-off-by: Andi Kleen Signed

[PATCH 4.9 95/96] selftests/x86: Add test_vsyscall

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 352909b49ba0d74929b96af6dfbefc854ab6ebb5 upstream. This tests that the vsyscall entries do what they're expected to do. It also confirms that attempts to read the vsyscal

Re: [PATCH V3 1/2] nvme: split resetting state into reset_prepate and resetting

On 1/14/2018 11:48 AM, Sagi Grimberg wrote: Currently, the ctrl->state will be changed to NVME_CTRL_RESETTING before queue the reset work. This is not so strict. There could be a big gap before the reset_work callback is invoked. In addition, there is some disable work in the reset_work callb

[PATCH 4.9 66/96] x86/Documentation: Add PTI description

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dave Hansen commit 01c9b17bf673b05bb401b76ec763e9730ccf1376 upstream. Add some details about how PTI works, what some of the downsides are, and how to debug it when things go wrong. Also docum

[PATCH 4.9 96/96] x86/retpoline: Remove compile time warning

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit b8b9ce4b5aec8de9e23cabb0a26b78641f9ab1d6 upstream. Remove the compile time warning when CONFIG_RETPOLINE=y and the compiler does not have retpoline support. Linus rationa

Re: [PATCH v4] mm/memcg: try harder to decrease [memory,memsw].limit_in_bytes

On Mon 15-01-18 15:30:59, Andrey Ryabinin wrote: > > > On 01/12/2018 03:24 PM, Michal Hocko wrote: > > On Fri 12-01-18 00:59:38, Andrey Ryabinin wrote: > >> On 01/11/2018 07:29 PM, Michal Hocko wrote: > > [...] > >>> I do not think so. Consider that this reclaim races with other > >>> reclaimers.

[PATCH 4.9 68/96] x86/cpufeatures: Make CPU bugs sticky

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 6cbd2171e89b13377261d15e64384df60ecb530e upstream. There is currently no way to force CPU bug bits like CPU feature bits. That makes it impossible to set a bug bit once a

[PATCH 4.9 70/96] x86/pti: Rename BUG_CPU_INSECURE to BUG_CPU_MELTDOWN

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit de791821c295cc61419a06fe5562288417d1bc58 upstream. Use the name associated with the particular attack which needs page table isolation for mitigation. Signed-off-by: Tho

linux-next: Signed-off-by missing for commit in the device-mapper tree

Hi all, Commit 34e1467da673 ("Revert "genirq/affinity: assign vectors to all possible CPUs"") is missing a Signed-off-by from its author and committer. Reverts are commits as well. Though I do note it actually has a reasonable commit message, thanks. -- Cheers, Stephen Rothwell

[PATCH 4.9 62/96] staging: android: ashmem: fix a race condition in ASHMEM_SET_SIZE ioctl

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Viktor Slavkovic commit 443064cb0b1fb4569fe0a71209da7625129fb760 upstream. A lock-unlock is missing in ASHMEM_SET_SIZE ioctl which can result in a race condition when mmap is called. After the

[PATCH] fix drm-get-put.cocci warnings

From: Fengguang Wu Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference() and drm_*_unreference() helpers. Generated by: scripts/coccinelle/api/drm-get-put.cocci Signed-off-by: Fengguang Wu Signed-off-by: Julia Lawall --- tree: https://github.com/thierryreding/linux for-4.16/

[PATCH 4.9 71/96] x86/cpufeatures: Add X86_BUG_SPECTRE_V[12]

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit 99c6fa2511d8a683e61468be91b83f85452115fa upstream. Add the bug bits for spectre v1/2 and force them unconditionally for all cpus. Signed-off-by: David Woodhouse Signed-

[PATCH 4.14 005/118] IB/srpt: Disable RDMA access by the initiator

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit bec40c26041de61162f7be9d2ce548c756ce0f65 upstream. With the SRP protocol all RDMA operations are initiated by the target. Since no RDMA operations are initiated by the i

[PATCH 4.14 000/118] 4.14.14-stable review

This is the start of the stable review cycle for the 4.14.14 release. There are 118 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Wed Jan 17 12:33:32 UTC 2018. Anything recei

[PATCH 4.14 004/118] can: gs_usb: fix return value of the "set_bittiming" callback

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Wolfgang Grandegger commit d5b42e6607661b198d8b26a0c30969605b1bf5c7 upstream. The "set_bittiming" callback treats a positive return value as error! For that reason "can_changelink()" will quit

Re: [PATCH v3] firmware: qcom: scm: Fix incorrect of_node_put calls in scm_init

Hello guys, Any news on this fix ? Anything else you need on my side ? Thanks On 15/12/2017 14:40, Loys Ollivier wrote: > When using other platform architectures, in the init of the qcom_scm > driver, of_node_put is called on /firmware if no qcom dt is found. > This results in a kernel error: B

[PATCH 4.14 016/118] platform/x86: wmi: Call acpi_wmi_init() later

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit 98b8e4e5c17bf87c1b18ed929472051dab39878c upstream. Calling acpi_wmi_init() at the subsys_initcall() level causes ordering issues to appear on some systems and they are

[PATCH 4.14 007/118] MIPS: Validate PR_SET_FP_MODE prctl(2) requests against the ABI of the task

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit b67336eee3fcb8ecedc6c13e2bf88aacfa3151e2 upstream. Fix an API loophole introduced with commit 9791554b45a2 ("MIPS,prctl: add PR_[GS]ET_FP_MODE prctl options for MIPS")

[PATCH 4.14 003/118] can: vxcan: improve handling of missing peer name attribute

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Hartkopp commit b4c2951a4833e66f1bbfe65ddcd4fdcdfafe5e8f upstream. Picking up the patch from Serhey Popovych (commit 191cdb3822e5df6b3c8, "veth: Be more robust on network device creatio

[PATCH 4.14 017/118] iw_cxgb4: only call the cq comp_handler when the cq is armed

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steve Wise commit cbb40fadd31c6bbc59104e58ac95c6ef492d038b upstream. The ULPs completion handler should only be called if the CQ is armed for notification. Signed-off-by: Steve Wise Signed-o

[PATCH 4.14 019/118] iw_cxgb4: only clear the ARMED bit if a notification is needed

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steve Wise commit 335ebf6fa35ca1c59b73f76fad19b249d3550e86 upstream. In __flush_qp(), the CQ ARMED bit was being cleared regardless of whether any notification is actually needed. This result

Re: [PATCH 4.14 053/118] Revert "Revert "xfrm: Fix stack-out-of-bounds read in xfrm_state_find.""

On Mon, Jan 15, 2018 at 01:34:40PM +0100, Greg Kroah-Hartman wrote: > 4.14-stable review patch. If anyone has any objections, please let me know. > > -- > > From: "David S. Miller" > > > This reverts commit 94802151894d482e82c324edf2c658f8e6b96508. > > It breaks transport mod

[PATCH 4.14 021/118] iw_cxgb4: when flushing, complete all wrs in a chain

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steve Wise commit d14587334580bc94d3ee11e8320e0c157f91ae8f upstream. If a wr chain was posted and needed to be flushed, only the first wr in the chain was completed with FLUSHED status. The r

[PATCH 4.14 023/118] ALSA: pcm: Remove incorrect snd_BUG_ON() usages

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit fe08f34d066f4404934a509b6806db1a4f700c86 upstream. syzkaller triggered kernel warnings through PCM OSS emulation at closing a stream: WARNING: CPU: 0 PID: 3502 at sound/c

[PATCH 4.14 024/118] ALSA: pcm: Workaround for weird PulseAudio behavior on rewind error

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit fb51f1cd06f9ced7b7085a2a4636375d520431ca upstream. The commit 9027c4639ef1 ("ALSA: pcm: Call ack() whenever appl_ptr is updated") introduced the possible error code returne

Re: [PATCH 0/2] PM / core: genpd fix and pm_runtime_force_suspend|resume() rework

Hi Rafael, On Mon, Jan 15, 2018 at 9:16 AM, Geert Uytterhoeven wrote: > On Mon, Jan 15, 2018 at 1:04 AM, Rafael J. Wysocki wrote: >> On Sun, Jan 14, 2018 at 10:48 AM, Geert Uytterhoeven >> wrote: >>> On Sat, Jan 13, 2018 at 1:38 AM, Rafael J. Wysocki >>> wrote: On Friday, January 12, 201

[PATCH 4.14 008/118] MIPS: Factor out NT_PRFPREG regset access helpers

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit a03fe72572c12e98f4173f8a535f32468e48b6ec upstream. In preparation to fix a commit 72b22bbad1e7 ("MIPS: Don't assume 64-bit FP registers for FP regset") FCSR access reg

[PATCH 4.14 028/118] ALSA: aloop: Release cable upon open error path

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 9685347aa0a5c2869058ca6ab79fd8e93084a67f upstream. The aloop runtime object and its assignment in the cable are left even when opening a substream fails. This doesn't mean

[PATCH 4.14 025/118] ALSA: pcm: Add missing error checks in OSS emulation plugin builder

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 6708913750344a900f2e73bfe4a4d6dbbce4fe8d upstream. In the OSS emulation plugin builder where the frame size is parsed in the plugin chain, some places miss the possible err

[PATCH 4.14 029/118] ALSA: aloop: Fix inconsistent format due to incomplete rule

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit b088b53e20c7d09b5ab84c5688e609f478e5c417 upstream. The extra hw constraint rule for the formats the aloop driver introduced has a slight flaw, where it doesn't return a pos

Re: [PATCH v2] perf trace: Fix missing handling of --call-graph dwarf

Em Mon, Jan 15, 2018 at 10:11:02AM +0100, Thomas-Mich Richter escreveu: > On 01/12/2018 09:02 PM, Arnaldo Carvalho de Melo wrote: > > Em Fri, Jan 12, 2018 at 01:47:06PM -0300, Arnaldo Carvalho de Melo escreveu: > >> There is still room for improvement, I noticed overriding is not working > >> for t

[PATCH 4.14 032/118] 8021q: fix a memory leak for VLAN 0 device

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit 78bbb15f2239bc8e663aa20bbe1987c91a0b75f6 ] A vlan device with vid 0 is allow to creat by not able to be fully cleaned up by unregister_vlan_dev() which checks for

[PATCH 4.14 035/118] phylink: ensure we report link down when LOS asserted

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Russell King [ Upstream commit ac817f5ad066697e4d4d35ec68c974eba2c5f17a ] Although we disable the netdev carrier, we fail to report in the kernel log that the link went down. Fix this. Fixe

[PATCH 4.14 033/118] ip6_tunnel: disable dst caching if tunnel is dual-stack

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eli Cooper [ Upstream commit 23263ec86a5f44312d2899323872468752324107 ] When an ip6_tunnel is in mode 'any', where the transport layer protocol can be either 4 or 41, dst_cache must be disabl

[PATCH 4.14 036/118] RDS: Heap OOB write in rds_message_alloc_sgs()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mohamed Ghannam [ Upstream commit c095508770aebf1b9218e77026e48345d719b17c ] When args->nr_local is 0, nr_pages gets also 0 due some size calculation via rds_rm_size(), which is later used to

[PATCH 4.14 034/118] net: core: fix module type in sock_diag_bind

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andrii Vladyka [ Upstream commit b8fd0823e0770c2d5fdbd865bccf0d5e058e5287 ] Use AF_INET6 instead of AF_INET in IPv6-related code path Signed-off-by: Andrii Vladyka Signed-off-by: David S. M

[PATCH 4.14 042/118] sctp: fix the handling of ICMP Frag Needed for too small MTUs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marcelo Ricardo Leitner [ Upstream commit b6c5734db07079c9410147b32407f2366d584e6c ] syzbot reported a hang involving SCTP, on which it kept flooding dmesg with the message: [ 246.742374] sc

[PATCH 4.14 038/118] net: fec: restore dev_id in the cases of probe error

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Fugang Duan [ Upstream commit e90f686b4358d7d7e5dbaa48b8e78c9a4e41826e ] The static variable dev_id always plus one before netdev registerred. It should restore the dev_id value in the cases

[PATCH 4.14 041/118] sctp: do not retransmit upon FragNeeded if PMTU discovery is disabled

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marcelo Ricardo Leitner [ Upstream commit cc35c3d1edf7a8373a1a5daa80a912dec96a9cd5 ] Currently, if PMTU discovery is disabled on a given transport, but the configured value is higher than the

[PATCH 4.14 039/118] net: fec: defer probe if regulator is not ready

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Fugang Duan [ Upstream commit 3f38c683033a9a0a2738e7067f449deefabfa3ef ] Defer probe if regulator is not ready. E.g. some regulator is fixed regulator controlled by i2c expander gpio, the i2c

[PATCH 3/3] mfd/omap-usb-tll: Return an error code only as a constant in usbtll_omap_probe()

From: Markus Elfring Date: Mon, 15 Jan 2018 14:00:45 +0100 * Return an error code without storing it in an intermediate variable. * Delete the label "err_clk_alloc" and local variable "ret" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring --- drivers/mfd/omap-us

[PATCH 4.14 011/118] MIPS: Fix an FCSR access API regression with NT_PRFPREG and MSA

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit be07a6a1188372b6d19a3307ec33211fc9c9439d upstream. Fix a commit 72b22bbad1e7 ("MIPS: Don't assume 64-bit FP registers for FP regset") public API regression, then activ

[PATCH 4.14 043/118] sh_eth: fix TSU resource handling

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sergei Shtylyov [ Upstream commit dfe8266b8dd10e12a731c985b725fcf7f0e537f0 ] When switching the driver to the managed device API, I managed to break the case of a dual Ether devices shari

[PATCH 4.14 044/118] net: stmmac: enable EEE in MII, GMII or RGMII only

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jerome Brunet [ Upstream commit 879626e3a52630316d817cbda7cec9a5446d1d82 ] Note in the databook - Section 4.4 - EEE : " The EEE feature is not supported when the MAC is configured to use the

[PATCH 4.14 015/118] kvm: vmx: Scrub hardware GPRs at VM-exit

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jim Mattson commit 0cb5b30698fdc8f6b4646012e3acb4ddce430788 upstream. Guest GPR values are live in the hardware GPRs at VM-exit. Do not leave any guest values in hardware GPRs after the guest

[PATCH 2/3] mfd/omap-usb-tll: Improve a size determination in usbtll_omap_probe()

From: Markus Elfring Date: Mon, 15 Jan 2018 13:43:53 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. This issue was det

[PATCH 4.14 012/118] MIPS: Also verify sizeof `elf_fpreg_t with PTRACE_SETREGSET

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit 006501e039eec411842bb3150c41358867d320c2 upstream. Complement commit d614fd58a283 ("mips/ptrace: Preserve previous registers for short regset write") and like with the

[PATCH 4.14 014/118] cgroup: fix css_task_iter crash on CSS_TASK_ITER_PROC

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 74d0833c659a8a54735e5efdd44f4b225af68586 upstream. While teaching css_task_iter to handle skipping over tasks which aren't group leaders, bc2fb7ed089f ("cgroup: add @flags to

[PATCH 4.14 006/118] IB/srpt: Fix ACL lookup during login

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit a1ffa4670cb97ae3a4b3e8535d88be5f643f7c3b upstream. Make sure that the initiator port GUID is stored in ch->ini_guid. Note: when initiating a connection sgid and dgid mem

[PATCH 4.14 013/118] MIPS: Disallow outsized PTRACE_SETREGSET NT_PRFPREG regset accesses

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit c8c5a3a24d395b14447a9a89d61586a913840a3b upstream. Complement commit c23b3d1a5311 ("MIPS: ptrace: Change GP regset to use correct core dump register layout") and also

[PATCH 1/3] mfd/omap-usb-tll: Delete two error messages for a failed memory allocation in usbtll_omap_probe()

From: Markus Elfring Date: Mon, 15 Jan 2018 13:39:25 +0100 Omit extra messages for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/mfd/omap-usb-tll.c | 5 + 1 file changed, 1 insertion(+), 4

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