Re: [PATCH] PCI: set flag IRQCHIP_ONESHOT_SAFE for PCI-MSI irqchip's

On Fri, 3 Aug 2018, Heiner Kallweit wrote: > PCI-MSI is oneshot-safe, therefore set flag IRQCHIP_ONESHOT_SAFE to > avoid unneeded masking/unmasking. See also discussion here: > https://marc.info/?l=linux-pci&m=153332526101128&w=2 This changelog really wants a bit more detailed information. > Sig

[PATCH 6/7] arm64: dts: allwinner: a64: Enable the THS on A64 boards

Enable the Thermal Sensor Controller on all A64 boards. Signed-off-by: Emmanuel Vadot --- arch/arm64/boot/dts/allwinner/sun50i-a64-amarula-relic.dts| 4 arch/arm64/boot/dts/allwinner/sun50i-a64-bananapi-m64.dts | 4 arch/arm64/boot/dts/allwinner/sun50i-a64-nanopi-a64.dts

[PATCH 1/7] dt-bindings: Add DT bindings documentation for Allwinner Thermal Sensor Controller

This patch adds documentation for Device-Tree bindings for the Allwinner Thermal Sensor Controller found on the H3, H5 and A64 SoCs Signed-off-by: Emmanuel Vadot --- .../bindings/thermal/allwinner-thermal.txt| 41 +++ 1 file changed, 41 insertions(+) create mode 100644 Docu

[PATCH 3/7] arm64: dts: allwinner: h5: Add thermal sensor controller node

This add the ths controller for the H5 and the nvmem cell for the calibration data on the sid node. Signed-off-by: Emmanuel Vadot --- arch/arm64/boot/dts/allwinner/sun50i-h5.dtsi | 19 +++ 1 file changed, 19 insertions(+) diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h5.dtsi

[PATCH 4/7] arm64: dts: allwinner: a64: Add thermal sensor controller node

This add the ths controller for the A64 and the nvmem cell for the calibration data on the sid node. Signed-off-by: Emmanuel Vadot --- arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 19 +++ 1 file changed, 19 insertions(+) diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64.d

[PATCH 7/7] arm64: dts: allwinner: H5: Enable the THS on H5 boards

Enable the Thermal Sensor Controller on all H5 boards. Signed-off-by: Emmanuel Vadot --- arch/arm64/boot/dts/allwinner/sun50i-h5-nanopi-neo-plus2.dts | 4 arch/arm64/boot/dts/allwinner/sun50i-h5-nanopi-neo2.dts | 4 arch/arm64/boot/dts/allwinner/sun50i-h5-orangepi-pc2.dts |

[PATCH 2/7] ARM: dts: sun8i: h3: Add thermal sensor controller node

This add the ths controller for the H3 and the nvmem cell for the calibration data on the sid node. Signed-off-by: Emmanuel Vadot --- arch/arm/boot/dts/sun8i-h3.dtsi | 19 +++ 1 file changed, 19 insertions(+) diff --git a/arch/arm/boot/dts/sun8i-h3.dtsi b/arch/arm/boot/dts/sun8i

[PATCH 5/7] ARM: dts: sun8i: h3: Enable the THS on H3 boards

Enable the Thermal Sensor Controller on all H3 boards. Signed-off-by: Emmanuel Vadot --- arch/arm/boot/dts/sun8i-h3-bananapi-m2-plus.dts | 4 arch/arm/boot/dts/sun8i-h3-beelink-x2.dts | 4 arch/arm/boot/dts/sun8i-h3-nanopi-m1-plus.dts | 4 arch/arm/boot/dts/sun8i-h3-nanopi

[PATCH] Staging: rtlwifi: base: fixed a brace coding style issue

Fixed a coding style issue Signed-off-by: Sohil Ladhani --- drivers/staging/rtlwifi/base.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/staging/rtlwifi/base.c b/drivers/staging/rtlwifi/base.c index 094827c1879a..654aa4e068ba 100644 --- a/drivers/staging/rtlwif

Re: [PATCH] Staging: rtlwifi: base: fixed a brace coding style issue

On Sat, 4 Aug 2018, Sohil Ladhani wrote: > Fixed a coding style issue This seems to fix the header problem. But it is a patch on the same code at the same place doing the same thing as the previous message. So you should say [PATCH v2] in the subject line, and then below the --- explain what

[PATCH v0] clk: rockchip: Add pclk_rkpwm_pmu to PMU critical clocks in rk3399

From: Levin Du PWM2 is commonly used to control voltage of PWM regulator of VDD_LOG in RK3399. On the Firefly-RK3399 board, PWM2 outputs 40 KHz square wave from power on and the VDD_LOG is about 0.9V. When the kernel boots normally into the system, the PWM2 keeps outputing PWM signal. But the ke

[PATCH] Staging: rtlwifi: base: Fixed line ending with parentheses

This patch fixes the "Lines should not end with a '('" problem reported by checkpatch Signed-off-by: Sohil Ladhani --- drivers/staging/rtlwifi/base.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/staging/rtlwifi/base.c b/drivers/staging/rtlwifi/base.c index 094

Re: [PATCH] Staging: rtlwifi: base: Fixed line ending with parentheses

On Sat, 4 Aug 2018, Sohil Ladhani wrote: > This patch fixes the "Lines should not end with a '('" problem reported by > checkpatch There is still no v2 in the subject line, or explanation of what has changed under the --- (I assume this is still the same place and the same code; I didn't keep

[PATCH 3/8] RISC-V: remove INTERRUPT_CAUSE_* defines from asm/irq.h

These are only of use to the local irq controller driver, so add them in that driver implementation instead, which will be submitted soon. Signed-off-by: Christoph Hellwig --- arch/riscv/include/asm/irq.h | 4 1 file changed, 4 deletions(-) diff --git a/arch/riscv/include/asm/irq.h b/arch/

[PATCH 1/8] RISC-V: remove timer leftovers

This code is currently unused and will be added back later in a different place with the real interrupt and clocksource support. Signed-off-by: Christoph Hellwig --- arch/riscv/kernel/time.c | 21 - 1 file changed, 21 deletions(-) diff --git a/arch/riscv/kernel/time.c b/arch

[PATCH 2/8] RISC-V: simplify software interrupt / IPI code

Rename handle_ipi to riscv_software_interrupt, drop the unused return value and move the prototype to irq.h together with riscv_timer_interupt. This allows simplifying the upcoming interrupt handling support. Signed-off-by: Christoph Hellwig --- arch/riscv/include/asm/irq.h | 1 + arch/riscv/inc

[PATCH 4/8] RISC-V: add a definition for the SIE SEIE bit

This mirrors the SIE_SSIE and SETE bits that are used in a similar fashion. Signed-off-by: Christoph Hellwig --- arch/riscv/include/asm/csr.h | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/riscv/include/asm/csr.h b/arch/riscv/include/asm/csr.h index 421fa3585798..28a0d1cb374c 100644 --

[PATCH 5/8] RISC-V: implement low-level interrupt handling

Add support for a routine that dispatches exceptions with the interrupt flags set to either the IPI or irqdomain code (and the clock source in the future). Loosely based on the irq-riscv-int.c irqchip driver from the RISC-V tree. Signed-off-by: Christoph Hellwig --- arch/riscv/kernel/entry.S |

simplified RISC-V interrupt and clocksource handling v3

This series tries adds support for interrupt handling and timers for the RISC-V architecture. The basic per-hart interrupt handling implemented by the scause and sie CSRs is extremely simple and implemented directly in arch/riscv/kernel/irq.c. In addition there is a irqchip driver for the PLIC ex

[PATCH 7/8] irqchip: add a SiFive PLIC driver

Adds a driver for the SiFive implementation of the RISC-V Platform Level Interrupt Controller (PLIC). The PLIC connects global interrupt sources to the local interrupt controller on each hart. This driver is based on the driver in the RISC-V tree from Palmer Dabbelt, but has been almost entirely

[PATCH 8/8] clocksource: new RISC-V SBI timer driver

From: Palmer Dabbelt The RISC-V ISA defines a per-hart real-time clock and timer, which is present on all systems. The clock is accessed via the 'rdtime' pseudo-instruction (which reads a CSR), and the timer is set via an SBI call. Contains various improvements from Atish Patra . Signed-off-by

[PATCH 6/8] dt-bindings: interrupt-controller: RISC-V PLIC documentation

From: Palmer Dabbelt This patch adds documentation for the platform-level interrupt controller (PLIC) found in all RISC-V systems. This interrupt controller routes interrupts from all the devices in the system to each hart-local interrupt controller. Note: the DTS bindings for the PLIC aren't s

Re: [PATCH] RISC-V: Don't use a global include guard for uapi/asm/syscalls.h

> index 818655b0d535..882a6aa09a33 100644 > --- a/arch/riscv/include/uapi/asm/syscalls.h > +++ b/arch/riscv/include/uapi/asm/syscalls.h > @@ -1,10 +1,11 @@ > -/* SPDX-License-Identifier: GPL-2.0 */ > +// SPDX-License-Identifier: GPL-2.0 /* */ is the required style for headers, // is only for other

[PATCH 4.17 13/31] can: ems_usb: Fix memory leak on ems_usb_disconnect()

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev commit 72c05f32f4a5055c9c8fe889bb6903ec959c0aad upstream. ems_usb_probe() allocates memory for dev->tx_msg_buffer, but there is no its deallocation in ems_usb_disconnect(). Fou

[PATCH 4.17 10/31] net/mlx5e: IPoIB, Set the netdevice sw mtu in ipoib enhanced flow

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Feras Daoud [ Upstream commit 8e1d162d8e81838119de18b4ca1e302ce906f2a6 ] After introduction of the cited commit, mlx5e_build_nic_params receives the netdevice mtu in order to set the sw_mtu of

[PATCH 4.17 11/31] squashfs: more metadata hardening

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit d512584780d3e6a7cacb2f482834849453d444a1 upstream. Anatoly reports another squashfs fuzzing issue, where the decompression parameters themselves are in a compressed block

[PATCH 4.17 01/31] bonding: avoid lockdep confusion in bond_get_stats()

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7e2556e40026a1b0c16f37446ab398d5a5a892e4 ] syzbot found that the following sequence produces a LOCKDEP splat [1] ip link add bond10 type bond ip link add bond11

[PATCH 4.17 17/31] x86/efi: Access EFI MMIO data as unencrypted when SEV is active

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Brijesh Singh commit 9b788f32bee6b0b293a4bdfca4ad4bb0206407fb upstream. SEV guest fails to update the UEFI runtime variables stored in the flash. The following commit: 1379edd59673 ("x86/e

[PATCH 4.17 02/31] inet: frag: enforce memory limits earlier

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 56e2c94f055d328f5f6b0a5c1721cca2f2d4e0a1 ] We currently check current frags memory usage only when a new frag queue is created. This allows attackers to first co

[PATCH 4.17 14/31] net: socket: fix potential spectre v1 gadget in socketcall

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Jeremy Cline commit c8e8cd579bb4265651df8223730105341e61a2d1 upstream. 'call' is a user-controlled value, so sanitize the array index after the bounds check to avoid speculating past the bound

[PATCH 4.17 15/31] net: socket: Fix potential spectre v1 gadget in sock_is_registered

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Jeremy Cline commit e978de7a6d382ec378830ca2cf38e902df0b6d84 upstream. 'family' can be a user-controlled value, so sanitize it after the bounds check to avoid speculative out-of-bounds access.

[PATCH 4.17 03/31] ipv4: frags: handle possible skb truesize change

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 4672694bd4f1aebdab0ad763ae4716e89cb15221 ] ip_frag_queue() might call pskb_pull() on one skb that is already in the fragment queue. We need to take care of poss

[PATCH 4.17 05/31] netlink: Fix spectre v1 gadget in netlink_create()

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Jeremy Cline [ Upstream commit bc5b6c0b62b932626a135f516a41838c510c6eba ] 'protocol' is a user-controlled value, so sanitize it after the bounds check to avoid using it for speculative out-of-

[PATCH 4.17 04/31] net: dsa: Do not suspend/resume closed slave_dev

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli [ Upstream commit a94c689e6c9e72e722f28339e12dff191ee5a265 ] If a DSA slave network device was previously disabled, there is no need to suspend or resume it. Fixes: 244625491

[PATCH 4.17 16/31] virtio_balloon: fix another race between migration and ballooning

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Jiang Biao commit 89da619bc18d79bca5304724c11d4ba3b67ce2c6 upstream. Kernel panic when with high memory pressure, calltrace looks like, PID: 21439 TASK: 881be3afedd0 CPU: 16 COMMAND: "jav

[PATCH 4.17 06/31] net: stmmac: Fix WoL for PCI-based setups

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Jose Abreu [ Upstream commit b7d0f08e9129c45ed41bc0cfa8e77067881e45fd ] WoL won't work in PCI-based setups because we are not saving the PCI EP state before entering suspend state and not allo

[PATCH 4.17 09/31] net/mlx5e: Set port trust mode to PCP as default

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Or Gerlitz [ Upstream commit 2e8e70d249e8c5c79bf88bbb36bb68154ab15471 ] The hairpin offload code has dependency on the trust mode being PCP. Hence we should set PCP as the default for handlin

[PATCH 4.17 08/31] net/mlx5e: E-Switch, Initialize eswitch only if eswitch manager

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Eli Cohen [ Upstream commit 5f5991f36dce1e69dd8bd7495763eec2e28f08e7 ] Execute mlx5_eswitch_init() only if we have MLX5_ESWITCH_MANAGER capabilities. Do the same for mlx5_eswitch_cleanup(). F

[PATCH 4.17 00/31] 4.17.13-stable review

This is the start of the stable review cycle for the 4.17.13 release. There are 31 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 Mon Aug 6 08:26:21 UTC 2018. Anything receiv

[PATCH 4.17 07/31] rxrpc: Fix user call ID check in rxrpc_service_prealloc_one

4.17-stable review patch. If anyone has any objections, please let me know. -- From: YueHaibing [ Upstream commit c01f6c9b3207e52fc9973a066a856ddf7a0538d8 ] There just check the user call ID isn't already in use, hence should compare user_call_ID with xcall->user_call_ID, whic

[PATCH 4.17 29/31] drm/atomic: Check old_plane_state->crtc in drm_atomic_helper_async_check()

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Boris Brezillon commit 603ba2dfb338b307aebe95fe344c479a59b3a175 upstream. Async plane update is supposed to work only when updating the FB or FB position of an already enabled plane. That does

[PATCH 4.17 30/31] drm/atomic: Initialize variables in drm_atomic_helper_async_check() to make gcc happy

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Boris Brezillon commit de2d8db395c32d121d02871819444b631f73e0b6 upstream. drm_atomic_helper_async_check() declares the plane, old_plane_state and new_plane_state variables to iterate over all

[PATCH 4.14 01/23] bonding: avoid lockdep confusion in bond_get_stats()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7e2556e40026a1b0c16f37446ab398d5a5a892e4 ] syzbot found that the following sequence produces a LOCKDEP splat [1] ip link add bond10 type bond ip link add bond11

[PATCH 4.14 13/23] virtio_balloon: fix another race between migration and ballooning

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jiang Biao commit 89da619bc18d79bca5304724c11d4ba3b67ce2c6 upstream. Kernel panic when with high memory pressure, calltrace looks like, PID: 21439 TASK: 881be3afedd0 CPU: 16 COMMAND: "jav

[PATCH 4.17 27/31] crypto: padlock-aes - Fix Nano workaround data corruption

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu commit 46d8c4b28652d35dc6cfb5adf7f54e102fc04384 upstream. This was detected by the self-test thanks to Ard's chunking patch. I finally got around to testing this out on my ancient

[PATCH 4.14 12/23] net: socket: fix potential spectre v1 gadget in socketcall

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jeremy Cline commit c8e8cd579bb4265651df8223730105341e61a2d1 upstream. 'call' is a user-controlled value, so sanitize the array index after the bounds check to avoid speculating past the bound

[PATCH 4.17 20/31] kvm: x86: vmx: fix vpid leak

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Roman Kagan commit 63aff65573d73eb8dda4732ad4ef222dd35e4862 upstream. VPID for the nested vcpu is allocated at vmx_create_vcpu whenever nested vmx is turned on with the module parameter. Howe

[PATCH 4.17 31/31] scsi: sg: fix minor memory leak in error path

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Tony Battersby commit c170e5a8d222537e98aa8d4fddb667ff7a2ee114 upstream. Fix a minor memory leak when there is an error opening a /dev/sg device. Fixes: cc833acbee9d ("sg: O_EXCL and other lo

[PATCH 4.17 24/31] iwlwifi: add more card IDs for 9000 series

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit 0a5257bc6d89c2ae69b9bf955679cb4f89261874 upstream. Add new device IDs for the 9000 series. Cc: sta...@vger.kernel.org # 4.14 Signed-off-by: Emmanuel Grumbach Signed-

[PATCH 4.17 19/31] x86/entry/64: Remove %ebx handling from error_entry/exit

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit b3681dd548d06deb2e1573890829dff4b15abf46 upstream. error_entry and error_exit communicate the user vs. kernel status of the frame using %ebx. This is unnecessary -- the

[PATCH 4.14 11/23] can: ems_usb: Fix memory leak on ems_usb_disconnect()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev commit 72c05f32f4a5055c9c8fe889bb6903ec959c0aad upstream. ems_usb_probe() allocates memory for dev->tx_msg_buffer, but there is no its deallocation in ems_usb_disconnect(). Fou

[PATCH 4.17 28/31] drm/vc4: Reset ->{x, y}_scaling[1] when dealing with uniplanar formats

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Boris Brezillon commit a6a00918d4ad8718c3ccde38c02cec17f116b2fd upstream. This is needed to ensure ->is_unity is correct when the plane was previously configured to output a multi-planar forma

[PATCH 4.17 26/31] RDMA/uverbs: Expand primary and alt AV port checks

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein commit addb8a6559f0f8b5a37582b7ca698358445a55bf upstream. The commit cited below checked that the port numbers provided in the primary and alt AVs are legal. That is sufficie

[PATCH 4.17 21/31] audit: fix potential null dereference context->module.name

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Yi Wang commit b305f7ed0f4f494ad6f3ef5667501535d5a8fa31 upstream. The variable 'context->module.name' may be null pointer when kmalloc return null, so it's better to check it before using to a

[PATCH 4.17 23/31] userfaultfd: remove uffd flags from vma->vm_flags if UFFD_EVENT_FORK fails

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Mike Rapoport commit 31e810aa1033a7db50a2746cd34a2432237f6420 upstream. The fix in commit 0cbb4b4f4c44 ("userfaultfd: clear the vma->vm_userfaultfd_ctx if UFFD_EVENT_FORK fails") cleared the v

[PATCH 4.17 18/31] x86/apic: Future-proof the TSC_DEADLINE quirk for SKX

4.17-stable review patch. If anyone has any objections, please let me know. -- From: Len Brown commit d9e6dbcf28f383bf08e6a3180972f5722e514a54 upstream. All SKX with stepping higher than 4 support the TSC_DEADLINE, no matter the microcode version. Without this patch, upcoming

[PATCH 4.14 14/23] x86/apic: Future-proof the TSC_DEADLINE quirk for SKX

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Len Brown commit d9e6dbcf28f383bf08e6a3180972f5722e514a54 upstream. All SKX with stepping higher than 4 support the TSC_DEADLINE, no matter the microcode version. Without this patch, upcoming

[PATCH 4.14 15/23] x86/entry/64: Remove %ebx handling from error_entry/exit

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit b3681dd548d06deb2e1573890829dff4b15abf46 upstream. error_entry and error_exit communicate the user vs. kernel status of the frame using %ebx. This is unnecessary -- the

[PATCH 4.14 16/23] kvm: x86: vmx: fix vpid leak

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Roman Kagan commit 63aff65573d73eb8dda4732ad4ef222dd35e4862 upstream. VPID for the nested vcpu is allocated at vmx_create_vcpu whenever nested vmx is turned on with the module parameter. Howe

[PATCH 4.14 17/23] audit: fix potential null dereference context->module.name

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yi Wang commit b305f7ed0f4f494ad6f3ef5667501535d5a8fa31 upstream. The variable 'context->module.name' may be null pointer when kmalloc return null, so it's better to check it before using to a

[PATCH 4.14 19/23] iwlwifi: add more card IDs for 9000 series

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit 0a5257bc6d89c2ae69b9bf955679cb4f89261874 upstream. Add new device IDs for the 9000 series. Cc: sta...@vger.kernel.org # 4.14 Signed-off-by: Emmanuel Grumbach Signed-

[PATCH 4.9 13/32] tcp: do not aggressively quick ack after ECN events

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 522040ea5fdd1c33bbf75e1d7c7c0422b96a94ef ] ECN signals currently forces TCP to enter quickack mode for up to 16 (TCP_MAX_QUICKACKS) following incoming packets. W

[PATCH 4.14 00/23] 4.14.61-stable review

This is the start of the stable review cycle for the 4.14.61 release. There are 23 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 Mon Aug 6 08:26:30 UTC 2018. Anything receiv

[PATCH 4.9 01/32] ipv4: remove BUG_ON() from fib_compute_spec_dst

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Lorenzo Bianconi [ Upstream commit 9fc12023d6f51551d6ca9ed7e02ecc19d79caf17 ] Remove BUG_ON() from fib_compute_spec_dst routine and check in_dev pointer during flowi4 data structure initializat

[PATCH 4.14 09/23] squashfs: more metadata hardening

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit d512584780d3e6a7cacb2f482834849453d444a1 upstream. Anatoly reports another squashfs fuzzing issue, where the decompression parameters themselves are in a compressed block

[PATCH 4.9 10/32] netlink: Dont shift with UB on nlk->ngroups

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Safonov [ Upstream commit 61f4b23769f0cc72ae62c9a81cf08f0397d40da8 ] On i386 nlk->ngroups might be 32 or 0. Which leads to UB, resulting in hang during boot. Check for 0 ngroups and use

[PATCH 4.9 12/32] tcp: add max_quickacks param to tcp_incr_quickack and tcp_enter_quickack_mode

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 9a9c9b51e54618861420093ae6e9b50a961914c5 ] We want to add finer control of the number of ACK packets sent after ECN events. This patch is not changing current be

[PATCH 4.9 11/32] tcp: do not force quickack when receiving out-of-order packets

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit a3893637e1eb0ef5eb1bbc52b3a8d2dfa317a35d ] As explained in commit 9f9843a751d0 ("tcp: properly handle stretch acks in slow start"), TCP stacks have to consider ho

[PATCH 4.9 02/32] net: ena: Fix use of uninitialized DMA address bits field

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Gal Pressman [ Upstream commit 101f0cd4f2216d32f1b8a75a2154cf3997484ee2 ] UBSAN triggers the following undefined behaviour warnings: [...] [ 13.236124] UBSAN: Undefined behaviour in drivers/

[PATCH 4.9 19/32] inet: frag: enforce memory limits earlier

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 56e2c94f055d328f5f6b0a5c1721cca2f2d4e0a1 ] We currently check current frags memory usage only when a new frag queue is created. This allows attackers to first con

[PATCH 4.14 23/23] scsi: sg: fix minor memory leak in error path

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Tony Battersby commit c170e5a8d222537e98aa8d4fddb667ff7a2ee114 upstream. Fix a minor memory leak when there is an error opening a /dev/sg device. Fixes: cc833acbee9d ("sg: O_EXCL and other lo

[PATCH 4.14 04/23] net: dsa: Do not suspend/resume closed slave_dev

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli [ Upstream commit a94c689e6c9e72e722f28339e12dff191ee5a265 ] If a DSA slave network device was previously disabled, there is no need to suspend or resume it. Fixes: 244625491

[PATCH 4.9 18/32] bonding: avoid lockdep confusion in bond_get_stats()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7e2556e40026a1b0c16f37446ab398d5a5a892e4 ] syzbot found that the following sequence produces a LOCKDEP splat [1] ip link add bond10 type bond ip link add bond11

[PATCH 4.14 08/23] net/mlx5e: E-Switch, Initialize eswitch only if eswitch manager

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eli Cohen [ Upstream commit 5f5991f36dce1e69dd8bd7495763eec2e28f08e7 ] Execute mlx5_eswitch_init() only if we have MLX5_ESWITCH_MANAGER capabilities. Do the same for mlx5_eswitch_cleanup(). F

[PATCH 4.9 16/32] pinctrl: intel: Read back TX buffer state

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko Date: Thu, 24 Aug 2017 11:19:33 +0300 Subject: [PATCH 4.9 16/32] pinctrl: intel: Read back TX buffer state From: Andy Shevchenko commit d68b42e30bbacd24354d644f430d088435b15e83

[PATCH 4.14 03/23] ipv4: frags: handle possible skb truesize change

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 4672694bd4f1aebdab0ad763ae4716e89cb15221 ] ip_frag_queue() might call pskb_pull() on one skb that is already in the fragment queue. We need to take care of poss

[PATCH 4.9 17/32] sched/wait: Remove the lockless swait_active() check in swake_up*()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Boqun Feng commit 35a2897c2a306cca344ca5c0b43416707018f434 upstream. Steven Rostedt reported a potential race in RCU core because of swake_up(): CPU0CPU1

[PATCH 4.9 14/32] tcp: refactor tcp_ecn_check_ce to remove sk type cast

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Yousuk Seung [ Upstream commit f4c9f85f3b2cb7669830cd04d0be61192a4d2436 ] Refactor tcp_ecn_check_ce and __tcp_ecn_check_ce to accept struct sock* instead of tcp_sock* to clean up type casts. Th

[PATCH 4.14 07/23] rxrpc: Fix user call ID check in rxrpc_service_prealloc_one

4.14-stable review patch. If anyone has any objections, please let me know. -- From: YueHaibing [ Upstream commit c01f6c9b3207e52fc9973a066a856ddf7a0538d8 ] There just check the user call ID isn't already in use, hence should compare user_call_ID with xcall->user_call_ID, whic

[PATCH 4.14 05/23] netlink: Fix spectre v1 gadget in netlink_create()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jeremy Cline [ Upstream commit bc5b6c0b62b932626a135f516a41838c510c6eba ] 'protocol' is a user-controlled value, so sanitize it after the bounds check to avoid using it for speculative out-of-

[PATCH 4.14 06/23] net: stmmac: Fix WoL for PCI-based setups

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jose Abreu [ Upstream commit b7d0f08e9129c45ed41bc0cfa8e77067881e45fd ] WoL won't work in PCI-based setups because we are not saving the PCI EP state before entering suspend state and not allo

[PATCH 4.14 02/23] inet: frag: enforce memory limits earlier

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 56e2c94f055d328f5f6b0a5c1721cca2f2d4e0a1 ] We currently check current frags memory usage only when a new frag queue is created. This allows attackers to first co

[PATCH 4.9 15/32] tcp: add one more quick ack after after ECN events

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 15ecbe94a45ef88491ca459b26efdd02f91edb6d ] Larry Brakmo proposal ( https://patchwork.ozlabs.org/patch/935233/ tcp: force cwnd at least 2 in tcp_cwnd_reduction) ma

[PATCH 4.14 22/23] drm/vc4: Reset ->{x, y}_scaling[1] when dealing with uniplanar formats

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Boris Brezillon commit a6a00918d4ad8718c3ccde38c02cec17f116b2fd upstream. This is needed to ensure ->is_unity is correct when the plane was previously configured to output a multi-planar forma

[PATCH 4.14 20/23] RDMA/uverbs: Expand primary and alt AV port checks

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein commit addb8a6559f0f8b5a37582b7ca698358445a55bf upstream. The commit cited below checked that the port numbers provided in the primary and alt AVs are legal. That is sufficie

[PATCH 4.14 21/23] crypto: padlock-aes - Fix Nano workaround data corruption

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu commit 46d8c4b28652d35dc6cfb5adf7f54e102fc04384 upstream. This was detected by the self-test thanks to Ard's chunking patch. I finally got around to testing this out on my ancient

[PATCH 4.9 23/32] net: stmmac: Fix WoL for PCI-based setups

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jose Abreu [ Upstream commit b7d0f08e9129c45ed41bc0cfa8e77067881e45fd ] WoL won't work in PCI-based setups because we are not saving the PCI EP state before entering suspend state and not allow

[PATCH 4.9 03/32] net: fix amd-xgbe flow-control issue

4.9-stable review patch. If anyone has any objections, please let me know. -- From: tangpengpeng [ Upstream commit 7f3fc7ddf719cd6faaf787722c511f6918ac6aab ] If we enable or disable xgbe flow-control by ethtool , it does't work.Because the parameter is not properly assigned,so

[PATCH 4.9 22/32] netlink: Fix spectre v1 gadget in netlink_create()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jeremy Cline [ Upstream commit bc5b6c0b62b932626a135f516a41838c510c6eba ] 'protocol' is a user-controlled value, so sanitize it after the bounds check to avoid using it for speculative out-of-b

[PATCH 4.9 21/32] net: dsa: Do not suspend/resume closed slave_dev

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli [ Upstream commit a94c689e6c9e72e722f28339e12dff191ee5a265 ] If a DSA slave network device was previously disabled, there is no need to suspend or resume it. Fixes: 2446254915

[PATCH 4.9 04/32] net: lan78xx: fix rx handling before first packet is send

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Wahren [ Upstream commit 136f55f660192ce04af091642efc75d85e017364 ] As long the bh tasklet isn't scheduled once, no packet from the rx path will be handled. Since the tx path also schedu

[PATCH 4.9 20/32] ipv4: frags: handle possible skb truesize change

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 4672694bd4f1aebdab0ad763ae4716e89cb15221 ] ip_frag_queue() might call pskb_pull() on one skb that is already in the fragment queue. We need to take care of possi

[PATCH 4.9 27/32] net: socket: fix potential spectre v1 gadget in socketcall

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jeremy Cline commit c8e8cd579bb4265651df8223730105341e61a2d1 upstream. 'call' is a user-controlled value, so sanitize the array index after the bounds check to avoid speculating past the bounds

[PATCH 4.9 06/32] NET: stmmac: align DMA stuff to largest cache line length

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eugeniy Paltsev [ Upstream commit 9939a46d90c6c76f4533d534dbadfa7b39dc6acc ] As for today STMMAC_ALIGN macro (which is used to align DMA stuff) relies on L1 line length (L1_CACHE_BYTES). This i

[PATCH 4.9 29/32] kvm: x86: vmx: fix vpid leak

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Roman Kagan commit 63aff65573d73eb8dda4732ad4ef222dd35e4862 upstream. VPID for the nested vcpu is allocated at vmx_create_vcpu whenever nested vmx is turned on with the module parameter. Howev

[PATCH 4.9 26/32] can: ems_usb: Fix memory leak on ems_usb_disconnect()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev commit 72c05f32f4a5055c9c8fe889bb6903ec959c0aad upstream. ems_usb_probe() allocates memory for dev->tx_msg_buffer, but there is no its deallocation in ems_usb_disconnect(). Foun

[PATCH 4.9 09/32] netlink: Do not subscribe to non-existent groups

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Safonov [ Upstream commit 7acf9d4237c46894e0fa0492dd96314a41742e84 ] Make ABI more strict about subscribing to group > ngroups. Code doesn't check for that and it looks bogus. (one can s

[PATCH 4.9 05/32] net: mdio-mux: bcm-iproc: fix wrong getter and setter pair

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Anton Vasilyev [ Upstream commit b0753408aadf32c7ece9e6b765017881e54af833 ] mdio_mux_iproc_probe() uses platform_set_drvdata() to store md pointer in device, whereas mdio_mux_iproc_remove() res

[PATCH 4.9 07/32] tcp_bbr: fix bw probing to raise in-flight data for very small BDPs

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Neal Cardwell [ Upstream commit 383d470936c05554219094a4d364d964cb324827 ] For some very small BDPs (with just a few packets) there was a quantization effect where the target number of packets

[PATCH 4.9 28/32] virtio_balloon: fix another race between migration and ballooning

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jiang Biao commit 89da619bc18d79bca5304724c11d4ba3b67ce2c6 upstream. Kernel panic when with high memory pressure, calltrace looks like, PID: 21439 TASK: 881be3afedd0 CPU: 16 COMMAND: "java

  1   2   3   4   >