[PATCH v2] x86: consider effective protection attributes in W+X check

Using just the leaf page table entry flags would cause a false warning in case _PAGE_RW is clear or _PAGE_NX is set in a higher level entry. Hand through both the current entry's flags as well as the accumulated effective value (the latter as pgprotval_t instead of pgprot_t, as it's not an actual e

[PATCH 4.9 39/77] cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shilpasri G Bhat commit 3fa4680b860bf48b437d6a2c039789c4abe202ae upstream. Some OpenPOWER boxes can have same pstate values for nominal and pmin pstates. In these boxes the current code will no

Re: [PATCH 2/2] perf, tools, stat: Reset ids counter when retrying events

Em Wed, Feb 21, 2018 at 03:31:17PM +0100, Jiri Olsa escreveu: > On Thu, Oct 05, 2017 at 07:00:29PM -0700, Andi Kleen wrote: > > From: Andi Kleen > > ouch, sry for overlooking this > > > > > perf stat can retry opening events. After opening an file descriptor > > it adds the ids to the ecsel. Ea

Re: [PATCH 1/2] perf, tools, stat: Use xyarray dimensions to iterate fds

On Thu, Oct 05, 2017 at 07:00:28PM -0700, Andi Kleen wrote: > From: Andi Kleen > > Now that the xyarray stores the dimensions we can use those > to iterate over the FDs for a evsel. > > Signed-off-by: Andi Kleen Acked-by: Jiri Olsa thanks, jirka > --- > tools/perf/builtin-stat.c | 11 +

[PATCH 4.9 41/77] ocfs2: try a blocking lock before return AOP_TRUNCATED_PAGE

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Gang He commit ff26cc10aec128c3f86b5611fd5f59c71d49c0e3 upstream. If we can't get inode lock immediately in the function ocfs2_inode_lock_with_page() when reading a page, we should not return d

[PATCH 4.9 42/77] s390: fix handling of -1 in set{,fs}[gu]id16 syscalls

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eugene Syromiatnikov commit 6dd0d2d22aa363fec075cb2577ba273ac8462e94 upstream. For some reason, the implementation of some 16-bit ID system calls (namely, setuid16/setgid16 and setfsuid16/setfs

Re: [PATCH v2 1/2] KVM: x86: Add a framework for supporting MSR-based features

On 21/02/2018 15:15, Tom Lendacky wrote: > On 2/21/2018 5:41 AM, Paolo Bonzini wrote: >> On 16/02/2018 00:12, Tom Lendacky wrote: >>> +static u32 msr_based_features[] = { >>> +}; >>> + >>> +static unsigned int num_msr_based_features = >>> ARRAY_SIZE(msr_based_features); >>> + >>> bool kvm_valid_e

[PATCH 4.9 13/77] PCI: keystone: Fix interrupt-controller-node lookup

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit eac56aa3bc8af3d9b9850345d0f2da9d83529134 upstream. Fix child-node lookup during initialisation which was using the wrong OF-helper and ended up searching the whole device tr

Re: [PATCH 20/20] lightnvm: pblk: implement 2.0 support

BTW, there is a V3 for this patch at least, adding holes in the mapping bitmap to avoid the multiplications and divisions on the fast path, when the media format is not a power of two. I'll send it this week; just wanted to get this out for revision. Javier > On 21 Feb 2018, at 10.26, Javier Gonz

Re: [PATCH 2/2] perf, tools, stat: Reset ids counter when retrying events

On Thu, Oct 05, 2017 at 07:00:29PM -0700, Andi Kleen wrote: > From: Andi Kleen ouch, sry for overlooking this > > perf stat can retry opening events. After opening an file descriptor > it adds the ids to the ecsel. Each event keeps a running > count of ids. When we decide to close an evsel and

[PATCH v2] rtc: m48t59: use generic nvmem

Instead of adding a binary sysfs attribute from the driver (which suffers from a race condition as the attribute appears after the device), use the core to register an nvmem device. Signed-off-by: Alexandre Belloni --- Changes in v2: - set nvmem_cfg.size once pdata->offset is defined drivers/

[PATCH v3] Handle vendor defined behavior in tcpci_init, tcpci_set_vconn and export tcpci_irq. More operations can be extended in tcpci_data if needed. According to TCPCI specification, 4.4.5.2 ROLE_C

From: ShuFanLee Signed-off-by: ShuFanLee --- drivers/staging/typec/tcpci.c | 128 +- drivers/staging/typec/tcpci.h | 13 + 2 files changed, 115 insertions(+), 26 deletions(-) patch changelogs between v1 & v2 - Remove unnecessary i2c_client in the

[PATCH 4.9 45/77] ARM: dts: STi: Add gpio polarity for "hdmi,hpd-gpio" property

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Patrice Chotard commit 7ac1f59c09a61e6af6622df6809e003b0af07f3d upstream. The GPIO polarity is missing in the hdmi,hpd-gpio property, this fixes the following DT warnings: arch/arm/boot/dts/st

[PATCH 4.9 14/77] video: fbdev: atmel_lcdfb: fix display-timings lookup

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 9cb18db0701f6b74f0c45c23ad767b3ebebe37f6 upstream. Fix child-node lookup during probe, which ended up searching the whole device tree depth-first starting at the parent rath

[PATCH 4.9 59/77] selftests/x86: Do not rely on "int $0x80" in single_step_syscall.c

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit 4105c69703cdeba76f384b901712c9397b04e9c2 upstream. On 64-bit builds, we should not rely on "int $0x80" working (it only does if CONFIG_IA32_EMULATION=y is enabled). To

[PATCH 4.9 58/77] selftests/x86: Do not rely on "int $0x80" in test_mremap_vdso.c

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit 2cbc0d66de0480449c75636f55697c7ff3af61fc upstream. On 64-bit builds, we should not rely on "int $0x80" working (it only does if CONFIG_IA32_EMULATION=y is enabled). Wi

[PATCH 4.9 60/77] x86/speculation: Fix up array_index_nospec_mask() asm constraint

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit be3233fbfcb8f5acb6e3bcd0895c3ef9e100d470 upstream. Allow the compiler to handle @size as an immediate value or memory directly rather than allocating a register. Reported-b

[PATCH] iio: light: add driver for bh1730fvc chips

Ambient light sensor that supports visible light and IR measurements and configurable gain/integration time. Signed-off-by: Pierre Bourdon --- .../devicetree/bindings/iio/light/bh1730.txt | 15 + drivers/iio/light/Kconfig | 10 + drivers/iio/light/Makefile

[PATCH 4.9 63/77] selftests/x86/mpx: Fix incorrect bounds with old _sigfault

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Rui Wang commit 961888b1d76d84efc66a8f5604b06ac12ac2f978 upstream. For distributions with old userspace header files, the _sigfault structure is different. mpx-mini-test fails with the followin

[PATCH 4.9 61/77] nospec: Move array_index_nospec() parameter checking into separate macro

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit 8fa80c503b484ddc1abbd10c7cb2ab81f3824a50 upstream. For architectures providing their own implementation of array_index_mask_nospec() in asm/barrier.h, attempting to use WARN_

[PATCH 4.9 64/77] x86/cpu: Rename cpu_data.x86_mask to cpu_data.x86_stepping

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jia Zhang commit b399151cb48db30ad1e0e93dd40d68c6d007b637 upstream. x86_mask is a confusing name which is hard to associate with the processor's stepping. Additionally, correct an indent issue

[PATCH 4.9 46/77] ARM: dts: nomadik: add interrupt-parent for clcd

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit e8bfa0422469cdfc86be3f525f621b1d44d2481b upstream. The clcd device is lacking an interrupt-parent property, which makes the interrupt unusable and shows up as a warning wit

[PATCH 4.9 67/77] x86: fix build warnign with 32-bit PAE

4.9-stable review patch. If anyone has any objections, please let me know. -- I ran into a 4.9 build warning in randconfig testing, starting with the KAISER patches: arch/x86/kernel/ldt.c: In function 'alloc_ldt_struct': arch/x86/include/asm/pgtable_types.h:208:24: error: large

[PATCH 4.9 69/77] ARM: dts: exynos: fix RTC interrupt for exynos5410

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 5628a8ca14149ba4226e3bdce3a04c3b688435ad upstream. According to the comment added to exynos_dt_pmu_match[] in commit 8b283c025443 ("ARM: exynos4/5: convert pmu wakeup to st

[PATCH 4.9 70/77] ARM: pxa/tosa-bt: add MODULE_LICENSE tag

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 3343647813fdf0f2409fbf5816ee3e0622168079 upstream. Without this tag, we get a build warning: WARNING: modpost: missing MODULE_LICENSE() in arch/arm/mach-pxa/tosa-bt.o For

Re: [PATCH v4 5/6] extcon: add possibility to get extcon device by OF node

On Wed, Feb 21, 2018 at 10:55 AM, Andrzej Hajda wrote: > Since extcon property is not allowed in DT, extcon subsystem requires > another way to get extcon device. Lets try the simplest approach - get > edev by of_node. > +/* > + * extcon_get_edev_by_of_node - Get the extcon device from devicetree

[PATCH 4.9 71/77] arm64: dts: msm8916: Add missing #phy-cells

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Andersson commit b0ab681285aa66064f2de5b74191c0cabba381ff upstream. Add a missing #phy-cells to the dsi-phy, to silence dtc warning. Cc: Archit Taneja Fixes: 305410ffd1b2 ("arm64: dts:

[PATCH 4.9 73/77] arm: dts: mt2701: Add reset-cells

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Matthias Brugger commit ae72e95b5e4ded145bfc6926ad9457b74e3af41a upstream. The hifsys and ethsys needs the definition of the reset-cells property. Fix this. Reviewed-by: Rob Herring Signed-of

[PATCH 4.9 74/77] ARM: dts: Delete bogus reference to the charlcd

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit 586b2a4befad88cd87b372a1cea01e58c6811ea9 upstream. The EB MP board probably has a character LCD but the board manual does not really state which IRQ it has assigned to this

[PATCH 4.9 76/77] mmc: sdhci-of-esdhc: fix eMMC couldnt work after kexec

4.9-stable review patch. If anyone has any objections, please let me know. -- From: yinbo.zhu commit 97618aca1440b5addc5c3d78659d3e176be23b80 upstream. The bit eSDHC_TBCTL[TB_EN] couldn't be reset by eSDHC_SYSCTL[RSTA] which is used to reset for all. The driver should make sur

[PATCH 4.9 50/77] x86/entry/64/compat: Clear registers for compat syscalls, to reduce speculation attack surface

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 6b8cf5cc9965673951f1ab3f0e3cf23d06e3e2ee upstream. At entry userspace may have populated registers with values that could otherwise be useful in a speculative execution atta

[PATCH 4.9 51/77] compiler-gcc.h: Introduce __optimize function attribute

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit df5d45aa08f848b79caf395211b222790534ccc7 upstream. Create a new function attribute __optimize, which allows to specify an optimization level on a per-function basis.

[PATCH 4.9 49/77] arm: spear13xx: Fix spics gpio controllers warning

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar commit f8975cb1b8a36d0839b6365235778dd9df1d04ca upstream. This fixes the following warning by also sending the flags argument for gpio controllers: Property 'cs-gpios', cell 6 is

[PATCH 4.9 52/77] x86/speculation: Update Speculation Control microcode blacklist

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit 1751342095f0d2b36fa8114d8e12c5688c455ac4 upstream. Intel have retroactively blessed the 0xc2 microcode on Skylake mobile and desktop parts, and the Gemini Lake 0x22 micro

[PATCH 4.9 44/77] ARM: lpc3250: fix uda1380 gpio numbers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit ca32e0c4bf9ca4b87089c5a5ce945e5f2ec890da upstream. dtc warns about obviously incorrect GPIO numbers for the audio codec on both lpc32xx boards: arch/arm/boot/dts/lpc3250-p

[PATCH 4.14 010/167] kselftest: fix OOM in memory compaction test

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 4c1baad223906943b595a887305f2e8124821dad upstream. Running the compaction_test sometimes results in out-of-memory failures. When I debugged this, it turned out that the co

[PATCH 4.14 012/167] RDMA/rxe: Fix a race condition in rxe_requester()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 65567e41219888feec72fee1de98ccf1efbbc16d upstream. The rxe driver works as follows: * The send queue, receive queue and completion queues are implemented as circular b

[PATCH 4.14 011/167] RDMA/rxe: Fix a race condition related to the QP error state

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 6f301e06de4cf9ab7303f5acd43e64fcd4aa04be upstream. The following sequence: * Change queue pair state into IB_QPS_ERR. * Post a work request on the queue pair. Triggers

[PATCH 4.14 013/167] RDMA/rxe: Fix rxe_qp_cleanup()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit bb3ffb7ad48a21e98a5c64eb21103a74fd9f03f6 upstream. rxe_qp_cleanup() can sleep so it must be run in thread context and not in atomic context. This patch avoids that the f

[PATCH 4.14 017/167] mwifiex: resolve reset vs. remove()/shutdown() deadlocks

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Brian Norris commit a64e7a79dd6030479caad603c8d78e6c9c14904f upstream. Commit b014e96d1abb ("PCI: Protect pci_error_handlers->reset_notify() usage with device_lock()") resolves races between d

Re: [PATCH v2 2/7] i3c: Add core I3C infrastructure

Hi Greg, On Tue, 19 Dec 2017 10:36:43 +0100 Greg Kroah-Hartman wrote: > On Tue, Dec 19, 2017 at 10:28:58AM +0100, Boris Brezillon wrote: > > On Tue, 19 Dec 2017 10:21:19 +0100 > > Greg Kroah-Hartman wrote: > > > > > On Tue, Dec 19, 2017 at 10:13:36AM +0100, Boris Brezillon wrote: > > > > O

[PATCH 4.14 019/167] powerpc/radix: Remove trace_tlbie call from radix__flush_tlb_all

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mahesh Salgaonkar commit 8d81296cfcce89013a714feb8d25004a156f8181 upstream. radix__flush_tlb_all() is called only in kexec path in real mode and any tracepoints at this stage will make kexec t

[PATCH 4.14 020/167] powerpc/numa: Invalidate numa_cpu_lookup_table on cpu remove

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nathan Fontenot commit 1d9a090783bef19fe8cdec878620d22f05191316 upstream. When DLPAR removing a CPU, the unmapping of the cpu from a node in unmap_cpu_from_node() should also invalidate the CP

[PATCH 4.14 026/167] arm64: dts: msm8916: Correct ipc references for smsm

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Andersson commit 566bd8902e7fa20bd412ed753e09e89c1c96939c upstream. SMSM is not symmetrical, the incoming bits from WCNSS are available at index 6, but the outgoing host id for WCNSS is

[PATCH 4.14 027/167] ARM: lpc3250: fix uda1380 gpio numbers

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit ca32e0c4bf9ca4b87089c5a5ce945e5f2ec890da upstream. dtc warns about obviously incorrect GPIO numbers for the audio codec on both lpc32xx boards: arch/arm/boot/dts/lpc3250-

[PATCH 4.14 029/167] ARM: dts: nomadik: add interrupt-parent for clcd

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit e8bfa0422469cdfc86be3f525f621b1d44d2481b upstream. The clcd device is lacking an interrupt-parent property, which makes the interrupt unusable and shows up as a warning wi

[PATCH 4.14 030/167] arm: dts: mt7623: fix card detection issue on bananapi-r2

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sean Wang commit b96a696fb2a8dd1ee4e6cfee48dcac270fc53287 upstream. Fix that bananapi-r2 booting from SD-card would fail since incorrect polarity is applied to the previous setup with GPIO_ACT

[PATCH 4.14 006/167] IB/core: Fix two kernel warnings triggered by rxe registration

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 02ee9da347873699603d9ce0112a80b5dd69dea1 upstream. Eliminate the WARN_ONs that create following two warnings when registering an rxe device: WARNING: CPU: 2 PID: 1005 a

Re: [PATCH v2 01/21] lib/vsprintf: Print time and date in human readable format via %pt

On Wed, Feb 21, 2018 at 2:23 PM, Andy Shevchenko wrote: > On Wed, 2018-02-21 at 08:38 +0100, Rasmus Villemoes wrote: >> On 2018-02-21 00:55, Joe Perches wrote: >> > On Tue, 2018-02-20 at 23:43 +0200, Andy Shevchenko wrote: >> > > There are users which print time and date represented by content >>

[PATCH 4.14 008/167] IB/core: Avoid a potential OOPs for an unused optional parameter

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael J. Ruhl commit 2ff124d597c2df8696169ce0006fc974c49a4569 upstream. The ev_file is an optional parameter for CQ creation. If the parameter is not passed, the ev_file pointer will be NULL

[PATCH 4.14 000/167] 4.14.21-stable review

This is the start of the stable review cycle for the 4.14.21 release. There are 167 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 Fri Feb 23 12:44:42 UTC 2018. Anything recei

[PATCH 4.14 041/167] x86/entry/64/compat: Clear registers for compat syscalls, to reduce speculation attack surface

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 6b8cf5cc9965673951f1ab3f0e3cf23d06e3e2ee upstream. At entry userspace may have populated registers with values that could otherwise be useful in a speculative execution att

[PATCH 4.14 044/167] crypto: sun4i_ss_prng - fix return value of sun4i_ss_prng_generate

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Artem Savkov commit dd78c832ffaf86eb6434e56de4bc3bc31f03f771 upstream. According to crypto/rng.h generate function should return 0 on success and < 0 on error. Fixes: b8ae5c7387ad ("crypto: s

[PATCH 4.14 047/167] x86/mm/pti: Fix PTI comment in entry_SYSCALL_64()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nadav Amit commit 14b1fcc62043729d12e8ae00f8297ab2ffe9fa91 upstream. The comment is confusing since the path is taken when CONFIG_PAGE_TABLE_ISOLATION=y is disabled (while the comment says it

[PATCH 4.14 050/167] Revert "x86/speculation: Simplify indirect_branch_prediction_barrier()"

4.14-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit f208820a321f9b23d77d7eed89945d862d62a3ed upstream. This reverts commit 64e16720ea0879f8ab4547e3b9758936d483909b. We cannot call C functions like that, without marking a

[PATCH 4.14 046/167] powerpc/mm/radix: Split linear mapping on hot-unplug

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Balbir Singh commit 4dd5f8a99e791a8c6500e3592f3ce81ae7edcde1 upstream. This patch splits the linear mapping if the hot-unplug range is smaller than the mapping size. The code detects if the ma

Re: metag build errors in mainline kernel

On 02/21/2018 04:27 AM, James Hogan wrote: On Tue, Feb 20, 2018 at 03:44:43PM -0800, Guenter Roeck wrote: The following errors are seen when building the kernel with the latest available metag toolchain (4.2.4 (IMG-1.4.0.700)). Kernel version tested is (v4.16-rc2-64-gaf3e79d29555). metag:allmod

[PATCH 4.14 048/167] x86/speculation: Update Speculation Control microcode blacklist

4.14-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit 1751342095f0d2b36fa8114d8e12c5688c455ac4 upstream. Intel have retroactively blessed the 0xc2 microcode on Skylake mobile and desktop parts, and the Gemini Lake 0x22 micr

[PATCH 4.14 049/167] x86/speculation: Correct Speculation Control microcode blacklist again

4.14-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit d37fc6d360a404b208547ba112e7dabb6533c7fc upstream. Arjan points out that the Intel document only clears the 0xc2 microcode on *some* parts with CPUID 506E3 (INTEL_FAM6_S

Re: [PATCH v2 1/2] KVM: x86: Add a framework for supporting MSR-based features

On 2/21/2018 5:41 AM, Paolo Bonzini wrote: > On 16/02/2018 00:12, Tom Lendacky wrote: >> +static u32 msr_based_features[] = { >> +}; >> + >> +static unsigned int num_msr_based_features = ARRAY_SIZE(msr_based_features); >> + >> bool kvm_valid_efer(struct kvm_vcpu *vcpu, u64 efer) >> { >> if (

[PATCH 4.14 055/167] PM / runtime: Update links_count also if !CONFIG_SRCU

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lukas Wunner commit 433986c2c265d106d6a8e88006e0131fefc92b7b upstream. Commit baa8809f6097 (PM / runtime: Optimize the use of device links) added an invocation of pm_runtime_drop_link() to __d

[PATCH 4.14 056/167] PM: cpuidle: Fix cpuidle_poll_state_init() prototype

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit d7212cfb05ba802bea4dd6c90d61cfe6366ea224 upstream. Commit f85942207516 (x86: PM: Make APM idle driver initialize polling state) made apm_init() call cpuidle_poll_state

[PATCH 4.14 059/167] x86/entry/64: Merge the POP_C_REGS and POP_EXTRA_REGS macros into a single POP_REGS macro

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit 502af0d70843c2a9405d7ba1f79b4b0305aaf5f5 upstream. The two special, opencoded cases for POP_C_REGS can be handled by ASM macros. Signed-off-by: Dominik Brodowski Cc:

[PATCH 4.14 061/167] x86/entry/64: Introduce the PUSH_AND_CLEAN_REGS macro

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit 3f01daecd545e818098d84fd1ad43e19a508d705 upstream. Those instances where ALLOC_PT_GPREGS_ON_STACK is called just before SAVE_AND_CLEAR_REGS can trivially be replaced b

Re: [PATCH v2 1/3] HID: add driver for Valve Steam Controller

On Tue, Feb 20, 2018 at 8:33 PM, Rodrigo Rivas Costa wrote: > There are two ways to connect the Steam Controller: directly to the USB > or with the USB wireless adapter. Both methods are similar, but the > wireless adapter can connect up to 4 devices at the same time. > > The wired device will ap

[PATCH 4.14 034/167] drm/i915: add GT number to intel_device_info

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lionel Landwerlin commit 0890540e21cf1156b4cf960a4c1c734db4e816f9 upstream. Up to Coffeelake we could deduce this GT number from the device ID. This doesn't seem to be the case anymore. This c

[PATCH 4.14 060/167] x86/entry/64: Interleave XOR register clearing with PUSH instructions

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit f7bafa2b05ef25eda1d9179fd930b0330cf2b7d1 upstream. Same as is done for syscalls, interleave XOR with PUSH instructions for exceptions/interrupts, in order to minimize

[PATCH 4.14 064/167] x86/entry/64: Indent PUSH_AND_CLEAR_REGS and POP_REGS properly

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit 92816f571af81e9a71cc6f3dc8ce1e2fcdf7b6b8 upstream. ... same as the other macros in arch/x86/entry/calling.h Signed-off-by: Dominik Brodowski Cc: Andy Lutomirski Cc:

[PATCH 4.14 066/167] x86/entry/64: Remove the unused icebp macro

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Borislav Petkov commit b498c261107461d5c42140dfddd05df83d8ca078 upstream. That macro was touched around 2.5.8 times, judging by the full history linux repo, but it was unused even then. Get ri

[PATCH 4.14 067/167] selftests/x86: Fix vDSO selftest segfault for vsyscall=none

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit 198ee8e17502da2634f7366395db1d77630e0219 upstream. The vDSO selftest tries to execute a vsyscall unconditionally, even if it is not present on the test system (e.g. if

[PATCH 4.14 035/167] drm/i915/kbl: Change a KBL pci id to GT2 from GT1.5

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Anuj Phogat commit 41693fd5237397d3c61b311af0fda1f6f39297c2 upstream. See Mesa commit 9c588ff Cc: Matt Turner Cc: Rodrigo Vivi Signed-off-by: Anuj Phogat Reviewed-by: Rodrigo Vivi Signed-

[PATCH 4.14 037/167] x86/kexec: Make kexec (mostly) work in 5-level paging mode

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kirill A. Shutemov commit 5bf30316991d5bcda046343ee77d823cf16fdd03 upstream. Currently kexec() will crash when switching into a 5-level paging enabled kernel. I missed that we need to change

[PATCH 4.14 038/167] x86/xen: init %gs very early to avoid page faults with stack protector

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Juergen Gross commit 4f277295e54c5b7340e48efea3fc5cc21a2872b7 upstream. When running as Xen pv guest %gs is initialized some time after C code is started. Depending on stack protector usage th

[PATCH 4.14 078/167] x86/speculation: Add dependency

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit ea00f301285ea2f07393678cd2b6057878320c9d upstream. Joe Konno reported a compile failure resulting from using an MSR without inclusion of , and while the current code buil

[PATCH 4.14 040/167] x86/entry/64: Clear extra registers beyond syscall arguments, to reduce speculation attack surface

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 8e1eb3fa009aa7c0b944b3c8b26b07de0efb3200 upstream. At entry userspace may have (maliciously) populated the extra registers outside the syscall calling convention with arbit

[PATCH 4.14 036/167] x86/gpu: add CFL to early quirks

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lucas De Marchi commit 33aa69ed8aacd92dea12671e52eb3ca6ac2d7a49 upstream. CFL was missing from intel_early_ids[]. The PCI ID needs to be there to allow the memory region to be stolen, otherwis

[PATCH 4.14 079/167] kmemcheck: remove annotations

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Levin, Alexander (Sasha Levin) commit 4950276672fce5c241857540f8561c440663673d upstream. Patch series "kmemcheck: kill kmemcheck", v2. As discussed at LSF/MM, kill kmemcheck. KASan is a repl

[PATCH 4.14 085/167] selftests/x86/mpx: Fix incorrect bounds with old _sigfault

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rui Wang commit 961888b1d76d84efc66a8f5604b06ac12ac2f978 upstream. For distributions with old userspace header files, the _sigfault structure is different. mpx-mini-test fails with the followi

[PATCH 4.14 086/167] x86/cpu: Rename cpu_data.x86_mask to cpu_data.x86_stepping

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jia Zhang commit b399151cb48db30ad1e0e93dd40d68c6d007b637 upstream. x86_mask is a confusing name which is hard to associate with the processor's stepping. Additionally, correct an indent issu

[PATCH 4.14 084/167] x86/mm: Rename flush_tlb_single() and flush_tlb_one() to __flush_tlb_one_[user|kernel]()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 1299ef1d8870d2d9f09a5aadf2f8b2c887c2d033 upstream. flush_tlb_single() and flush_tlb_one() sound almost identical, but they really mean "flush one user translation" and "

[PATCH 4.14 083/167] kmemcheck: rip it out for real

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michal Hocko commit f335195adf043168ee69d78ea72ac3e30f0c57ce upstream. Commit 4675ff05de2d ("kmemcheck: rip it out") has removed the code but for some reason SPDX header stayed in place. This

[PATCH 4.14 087/167] x86/spectre: Fix an error message

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 9de29eac8d2189424d81c0d840cd0469aa3d41c8 upstream. If i == ARRAY_SIZE(mitigation_options) then we accidentally print garbage from one space beyond the end of the mitigatio

[PATCH 4.14 070/167] selftests/x86: Do not rely on "int $0x80" in test_mremap_vdso.c

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit 2cbc0d66de0480449c75636f55697c7ff3af61fc upstream. On 64-bit builds, we should not rely on "int $0x80" working (it only does if CONFIG_IA32_EMULATION=y is enabled). W

[PATCH 4.14 089/167] x86/entry/64: Fix CR3 restore in paranoid_exit()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ingo Molnar commit e48657573481a5dff7cfdc3d57005c80aa816500 upstream. Josh Poimboeuf noticed the following bug: "The paranoid exit code only restores the saved CR3 when it switches back to

[PATCH 4.14 082/167] kmemcheck: rip it out

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Levin, Alexander (Sasha Levin) commit 4675ff05de2d76d167336b368bd07f3fef6ed5a6 upstream. Fix up makefiles, remove references, and git rm kmemcheck. Link: http://lkml.kernel.org/r/20171007030

[PATCH 4.14 092/167] drm/qxl: unref cursor bo when finished with it

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ray Strode commit 16c6db3688734b27487a42d0c2a1062d0b2bad03 upstream. qxl_cursor_atomic_update allocs a bo for the cursor that it never frees up at the end of the function. This commit fixes t

[PATCH 4.14 094/167] drm/ast: Load lut in crtc_commit

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Vetter commit 24b8ef699e8221d2b7f813adaab13eec053e1507 upstream. In the past the ast driver relied upon the fbdev emulation helpers to call ->load_lut at boot-up. But since commit b8e2

[PATCH 4.14 088/167] x86/cpu: Change type of x86_cache_size variable to unsigned int

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit 24dbc6000f4b9b0ef5a9daecb161f1907733765a upstream. Currently, x86_cache_size is of type int, which makes no sense as we will never have a valid cache size equal or l

[PATCH 4.14 095/167] arm64: Add missing Falkor part number for branch predictor hardening

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Shanker Donthineni commit 16e574d762ac5512eb922ac0ac5eed360b7db9d8 upstream. References to CPU part number MIDR_QCOM_FALKOR were dropped from the mailing list patch due to mainline/arm64 branc

[PATCH 4.14 071/167] selftests/x86: Do not rely on "int $0x80" in single_step_syscall.c

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit 4105c69703cdeba76f384b901712c9397b04e9c2 upstream. On 64-bit builds, we should not rely on "int $0x80" working (it only does if CONFIG_IA32_EMULATION=y is enabled). To

[PATCH 4.14 099/167] mbcache: initialize entry->e_referenced in mb_cache_entry_create()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Potapenko commit 3876bbe27d04b848750d5310a37d6b76b593f648 upstream. KMSAN reported use of uninitialized |entry->e_referenced| in a condition in mb_cache_shrink(): ==

[PATCH 4.14 102/167] Revert "mmc: meson-gx: include tx phase in the tuning process"

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jerome Brunet commit fe0e58048f005fdce315eb4d185e5c160be4ac01 upstream. This reverts commit 0a44697627d17a66d7dc98f17aeca07ca79c5c20. This commit was initially intended to fix problems with h

[PATCH] iio:dummy: Fix coding style in simple_dummy and evgen

This patch fixes the following checkpatch.pl warnings: drivers/iio/dummy/iio_simple_dummy.c:603: WARNING: Block comments should align the * on each line drivers/iio/dummy/iio_dummy_evgen.c:151: WARNING: Symbolic permissions 'S_IWUSR' are not preferred. Consider using octal permissions '0200'... dr

Re: [PATCH v2 01/21] lib/vsprintf: Print time and date in human readable format via %pt

> TBH, I don't see much consensus among developers on this topic. > I wouldn't like to send a new version until it would be a consensus. I would love to see the comments followed by an agreement from majority of people who are in Cc list here. -- Andy Shevchenko Intel Finland Oy

[PATCH 4.14 073/167] objtool: Fix segfault in ignore_unreachable_insn()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Josh Poimboeuf commit fe24e27128252c230a34a6c628da2bf1676781ea upstream. Peter Zijlstra's patch for converting WARN() to use UD2 triggered a bunch of false "unreachable instruction" warnings,

[PATCH 4.14 077/167] nospec: Move array_index_nospec() parameter checking into separate macro

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit 8fa80c503b484ddc1abbd10c7cb2ab81f3824a50 upstream. For architectures providing their own implementation of array_index_mask_nospec() in asm/barrier.h, attempting to use WARN

[PATCH 4.14 076/167] x86/speculation: Fix up array_index_nospec_mask() asm constraint

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit be3233fbfcb8f5acb6e3bcd0895c3ef9e100d470 upstream. Allow the compiler to handle @size as an immediate value or memory directly rather than allocating a register. Reported-

Re: [PATCH v2 20/21] mk68/mac: Switch to use %ptR

On Wed, 2018-02-21 at 10:38 +0100, Geert Uytterhoeven wrote: > > + select PRINTK_PEXT_TIMEDATE > > Yeah, now you have to track whatever code uses the new %p extension... I don't like this. People had an opinion that 750+ bytes is way too much for tiny kernel configuration. -- Andy Shevch

[PATCH 4.14 068/167] selftests/x86: Clean up and document sscanf() usage

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Brodowski commit d8e92de8ef952bed88c56c7a44c02d8dcae0984e upstream. Replace a couple of magically connected buffer length literal constants with a common definition that makes their re

[PATCH 4.14 115/167] PCI: keystone: Fix interrupt-controller-node lookup

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit eac56aa3bc8af3d9b9850345d0f2da9d83529134 upstream. Fix child-node lookup during initialisation which was using the wrong OF-helper and ended up searching the whole device t

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