Re: [PATCH] ASoC: uniphier: evea: fix typo 'eva' -> 'evea'

2018-02-20 18:53 GMT+09:00 Katsuhiro Suzuki : Looks good to me:) Reviewed-by: Masami Hiramatsu Thanks, > Signed-off-by: Katsuhiro Suzuki > --- > sound/soc/uniphier/evea.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/sound/soc/uniphier/evea.c b/sound/soc/unip

Re: [PATCH 9/9] serial: xuartps: Fix out-of-bounds access through DT alias

On 20.2.2018 10:40, Geert Uytterhoeven wrote: > The cdns_uart_port[] array is indexed using a value derived from the > "serialN" alias in DT, which may lead to an out-of-bounds access. > > Fix this by adding a range check. > > Fixes: 1f118c02a1819856 ("serial: xuartps: Fix out-of-bounds access th

[PATCH] mmc: dw_mmc-k3: Fix out-of-bounds access through DT alias

The hs_timing_cfg[] array is indexed using a value derived from the "mshcN" alias in DT, which may lead to an out-of-bounds access. Fix this by adding a range check. Fixes: 7d92895208a008a2 ("mmc: dw_mmc-k3: Fix out-of-bounds access through DT alias") Signed-off-by: Geert Uytterhoeven --- Compi

[tip:x86/pti] x86/mm: Remove stale comment about KMEMCHECK

Commit-ID: 3b3a9268bba62b35a29bafe0931715b1725fdf26 Gitweb: https://git.kernel.org/tip/3b3a9268bba62b35a29bafe0931715b1725fdf26 Author: Jann Horn AuthorDate: Mon, 19 Feb 2018 18:50:39 +0100 Committer: Ingo Molnar CommitDate: Tue, 20 Feb 2018 09:33:39 +0100 x86/mm: Remove stale comment

[tip:x86/pti] x86/mm: Fix {pmd,pud}_{set,clear}_flags()

Commit-ID: 842cef9113c2120f74f645111ded1e020193d84c Gitweb: https://git.kernel.org/tip/842cef9113c2120f74f645111ded1e020193d84c Author: Jan Beulich AuthorDate: Mon, 19 Feb 2018 07:48:11 -0700 Committer: Ingo Molnar CommitDate: Tue, 20 Feb 2018 09:33:39 +0100 x86/mm: Fix {pmd,pud}_{set,

[tip:x86/pti] x86/asm: Improve how GEN_*_SUFFIXED_RMWcc() specify clobbers

Commit-ID: 700b7c5409c3e9da279fbea78cf28a78fbc176cd Gitweb: https://git.kernel.org/tip/700b7c5409c3e9da279fbea78cf28a78fbc176cd Author: Jan Beulich AuthorDate: Mon, 19 Feb 2018 07:49:12 -0700 Committer: Ingo Molnar CommitDate: Tue, 20 Feb 2018 09:33:39 +0100 x86/asm: Improve how GEN_*_

[tip:x86/pti] x86/IO-APIC: Avoid warning in 32-bit builds

Commit-ID: 6262b6e78ce5ba62be47774ca80f5b0a6f0eb428 Gitweb: https://git.kernel.org/tip/6262b6e78ce5ba62be47774ca80f5b0a6f0eb428 Author: Jan Beulich AuthorDate: Mon, 19 Feb 2018 07:50:23 -0700 Committer: Ingo Molnar CommitDate: Tue, 20 Feb 2018 09:33:40 +0100 x86/IO-APIC: Avoid warning

[tip:x86/pti] x86-64/realmode: Add instruction suffix

Commit-ID: 8554004a0231dedf44d4d62147fb3d6a6db489aa Gitweb: https://git.kernel.org/tip/8554004a0231dedf44d4d62147fb3d6a6db489aa Author: Jan Beulich AuthorDate: Mon, 19 Feb 2018 08:06:14 -0700 Committer: Ingo Molnar CommitDate: Tue, 20 Feb 2018 09:33:41 +0100 x86-64/realmode: Add instru

[tip:x86/pti] x86/LDT: Avoid warning in 32-bit builds with older gcc

Commit-ID: f2f18b16c779978ece4a04f304a92ff9ac8fbce5 Gitweb: https://git.kernel.org/tip/f2f18b16c779978ece4a04f304a92ff9ac8fbce5 Author: Jan Beulich AuthorDate: Mon, 19 Feb 2018 07:52:10 -0700 Committer: Ingo Molnar CommitDate: Tue, 20 Feb 2018 09:33:40 +0100 x86/LDT: Avoid warning in 3

[tip:x86/urgent] x86/headers/UAPI: Use __u64 instead of u64 in

Commit-ID: 894266466aa74a226e58e23975118ff6231dd2e4 Gitweb: https://git.kernel.org/tip/894266466aa74a226e58e23975118ff6231dd2e4 Author: KarimAllah Ahmed AuthorDate: Tue, 20 Feb 2018 08:39:51 +0100 Committer: Ingo Molnar CommitDate: Tue, 20 Feb 2018 08:54:47 +0100 x86/headers/UAPI: Use

Re: [PATCH 3/9] serial: imx: Fix out-of-bounds access through DT alias

Hello Geert, On Tue, Feb 20, 2018 at 10:40:18AM +0100, Geert Uytterhoeven wrote: > The imx_ports[] array is indexed using a value derived from the > "serialN" alias in DT, which may lead to an out-of-bounds access. > > Fix this by adding a range check. > > Fixes: 9206ab8a0350c3da ("serial: imx:

[PATCH 0/2] MIPS: CONFIG_SMP_SINGLE_IPI

This series adds a configuration option to allow MIPS kernels using CONFIG_GENERIC_IRQ_IPI to use only a single IPI per CPU rather than the usual 2. This allows these kernels to boot on hardware with insufficient interrupts for the usual 2 / CPU. It may also prove more flexible in allowing greater

[PATCH 1/2] MIPS: SMP: Group CONFIG_GENERIC_IRQ_IPI together

In preparation for allowing selection of a single IPI / CPU, group affected code together to minimise ifdeffery. Signed-off-by: Matt Redfearn --- arch/mips/kernel/smp.c | 11 --- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/arch/mips/kernel/smp.c b/arch/mips/kernel/smp.

[tip:x86/pti] Revert "x86/retpoline: Simplify vmexit_fill_RSB()"

Commit-ID: d1c99108af3c5992640aa2afa7d2e88c3775c06e Gitweb: https://git.kernel.org/tip/d1c99108af3c5992640aa2afa7d2e88c3775c06e Author: David Woodhouse AuthorDate: Mon, 19 Feb 2018 10:50:56 + Committer: Ingo Molnar CommitDate: Tue, 20 Feb 2018 09:38:26 +0100 Revert "x86/retpoline:

[PATCH 2/2] MIPS: SMP: Introduce CONFIG_SMP_SINGLE_IPI

Introduce a new Kconfig option which allows selection of a single IPI per CPU rather than the usual 2 on platforms using CONFIG_GENERIC_IRQ_IPI. This introduces a new IPI mechanism in which a bitmask of requested IPIs is kept per cpu. A bit is atomically set in the target CPUs mask when requesting

[tip:x86/pti] x86/speculation: Use IBRS if available before calling into firmware

Commit-ID: dd84441a797150dcc49298ec95c459a8891d8bb1 Gitweb: https://git.kernel.org/tip/dd84441a797150dcc49298ec95c459a8891d8bb1 Author: David Woodhouse AuthorDate: Mon, 19 Feb 2018 10:50:54 + Committer: Ingo Molnar CommitDate: Tue, 20 Feb 2018 09:38:33 +0100 x86/speculation: Use IB

Re: [PATCH 16/18] crypto: talitos - do hw_context DMA mapping outside the requests

On Mon, Feb 19, 2018 at 01:16:30PM +, Horia Geantă wrote: > > > And what about ALGIF path from user space ? > > What if the user never calls the last sendmsg() which will call > > hash_finup() ? > > > User is expected to follow the rules of the crypto API. > Of course, kernel won't (or at lea

[tip:x86/boot] x86/xen: Add pvh specific rsdp address retrieval function

Commit-ID: e9cb8fc2e5ca5996417f900ed5149bd9150f6abd Gitweb: https://git.kernel.org/tip/e9cb8fc2e5ca5996417f900ed5149bd9150f6abd Author: Juergen Gross AuthorDate: Mon, 19 Feb 2018 11:09:06 +0100 Committer: Ingo Molnar CommitDate: Tue, 20 Feb 2018 09:00:56 +0100 x86/xen: Add pvh specific

[tip:x86/boot] x86/acpi: Add a new x86_init_acpi structure to x86_init_ops

Commit-ID: 62d8b7fba8d3ba9c046b7a1a95946c6aaf7c5da9 Gitweb: https://git.kernel.org/tip/62d8b7fba8d3ba9c046b7a1a95946c6aaf7c5da9 Author: Juergen Gross AuthorDate: Mon, 19 Feb 2018 11:09:05 +0100 Committer: Ingo Molnar CommitDate: Tue, 20 Feb 2018 09:00:56 +0100 x86/acpi: Add a new x86_i

Re: [PATCH v3 2/4] x86/speculation: Support "Enhanced IBRS" on future CPUs

On Tue, 20 Feb 2018, David Woodhouse wrote: > On Tue, 2018-02-20 at 09:31 +0100, Thomas Gleixner wrote: > > > @@ -3387,13 +3387,14 @@ static int vmx_set_msr(struct kvm_vcpu *vcpu, > > > struct msr_data *msr_info) > > >   > > >   vmx->spec_ctrl = data; > > >   > > > - if (!data) > >

[tip:x86/boot] acpi: Introduce acpi_arch_get_root_pointer() for getting rsdp address

Commit-ID: 795e2963a1afef44ed9ec7e6d16c8052fcd8d886 Gitweb: https://git.kernel.org/tip/795e2963a1afef44ed9ec7e6d16c8052fcd8d886 Author: Juergen Gross AuthorDate: Mon, 19 Feb 2018 11:09:04 +0100 Committer: Ingo Molnar CommitDate: Tue, 20 Feb 2018 09:00:55 +0100 acpi: Introduce acpi_arch

Re: [PATCH 9/9] serial: xuartps: Fix out-of-bounds access through DT alias

Hi Michal, On Tue, Feb 20, 2018 at 11:22 AM, Michal Simek wrote: > On 20.2.2018 10:40, Geert Uytterhoeven wrote: >> The cdns_uart_port[] array is indexed using a value derived from the >> "serialN" alias in DT, which may lead to an out-of-bounds access. >> >> Fix this by adding a range check. >>

Re: [PATCH v4] reset: add support for non-DT systems

Hi Bartosz, David, On Mon, 2018-02-19 at 18:21 -0600, David Lechner wrote: > On 02/19/2018 10:58 AM, Bartosz Golaszewski wrote: > > From: Bartosz Golaszewski > > > > The reset framework only supports device-tree. There are some platforms > > however, which need to use it even in legacy, board-fi

[tip:x86/pti] x86/retpoline: Support retpoline builds with Clang

Commit-ID: 87358710c1fb4f1bf96bbe2349975ff9953fc9b2 Gitweb: https://git.kernel.org/tip/87358710c1fb4f1bf96bbe2349975ff9953fc9b2 Author: David Woodhouse AuthorDate: Mon, 19 Feb 2018 10:50:57 + Committer: Ingo Molnar CommitDate: Tue, 20 Feb 2018 11:17:58 +0100 x86/retpoline: Support

Re: [PATCH 4.9 00/92] 4.9.81-stable review

On Sat, Feb 17, 2018 at 09:35:59AM -0800, Guenter Roeck wrote: > On 02/17/2018 05:45 AM, Greg Kroah-Hartman wrote: > > On Sat, Feb 17, 2018 at 02:31:53PM +0100, Yves-Alexis Perez wrote: > > > On Tue, 2018-02-13 at 16:29 +0100, Greg Kroah-Hartman wrote: > > > > > arch/powerpc/kernel/entry_64.S: Asse

Re: [PATCH v6 0/4] x86, kasan: add KASAN checks to atomic operations

On Wed, Feb 7, 2018 at 3:17 PM, Dmitry Vyukov wrote: > On Wed, Jan 31, 2018 at 5:17 PM, Will Deacon wrote: >>> > * Will Deacon wrote: >>> >> e.g. for atomic[64]_read, your asm-generic header looks like: >>> >> >>> >> #ifndef _LINUX_ATOMIC_INSTRUMENTED_H >>> >> #define _LINUX_ATOMIC_INSTRUMENTED_

Re: [RFCv4 01/21] media: add request API core and UAPI

On 02/20/18 05:44, Alexandre Courbot wrote: > The request API provides a way to group buffers and device parameters > into units of work to be queued and executed. This patch introduces the > UAPI and core framework. > > This patch is based on the previous work by Laurent Pinchart. The core > has

Re: [PATCH v3 2/4] x86/speculation: Support "Enhanced IBRS" on future CPUs

On Tue, 20 Feb 2018, Thomas Gleixner wrote: > On Tue, 20 Feb 2018, David Woodhouse wrote: > > On Tue, 2018-02-20 at 09:31 +0100, Thomas Gleixner wrote: > > > > @@ -3387,13 +3387,14 @@ static int vmx_set_msr(struct kvm_vcpu *vcpu, > > > > struct msr_data *msr_info) > > > >   > > > >  

Re: Patch "[Variant 2/Spectre-v2] arm64: Implement branch predictor hardening for Falkor" has been added to the 4.14-stable tree

On Mon, Feb 19, 2018 at 06:57:12PM -0500, Jon Masters wrote: > On 02/14/2018 11:16 AM, Timur Tabi wrote: > > On Wed, Feb 14, 2018 at 7:53 AM, wrote: > >> > >> This is a note to let you know that I've just added the patch titled > >> > >> [Variant 2/Spectre-v2] arm64: Implement branch predicto

Re: Patch "[Variant 2/Spectre-v2] arm64: Implement branch predictor hardening for Falkor" has been added to the 4.14-stable tree

On Tue, Feb 20, 2018 at 11:47:38AM +0100, Greg Kroah-Hartman wrote: > On Mon, Feb 19, 2018 at 06:57:12PM -0500, Jon Masters wrote: > > On 02/14/2018 11:16 AM, Timur Tabi wrote: > > > On Wed, Feb 14, 2018 at 7:53 AM, wrote: > > >> > > >> This is a note to let you know that I've just added the patc

Re: [PATCH 1/9] serial: arc_uart: Fix out-of-bounds access through DT alias

On Tue, Feb 20, 2018 at 10:40 AM, Geert Uytterhoeven wrote: > The arc_uart_ports[] array is indexed using a value derived from the > "serialN" alias in DT, which may lead to an out-of-bounds access. > > Fix this by adding a range check. > > Note that the array size is defined by a Kconfig symbol >

Re: [PATCH 3/9] serial: imx: Fix out-of-bounds access through DT alias

Hi Uwe, On Tue, Feb 20, 2018 at 11:31 AM, Uwe Kleine-König wrote: > On Tue, Feb 20, 2018 at 10:40:18AM +0100, Geert Uytterhoeven wrote: >> The imx_ports[] array is indexed using a value derived from the >> "serialN" alias in DT, which may lead to an out-of-bounds access. >> >> Fix this by adding

RE: [lustre-devel] [PATCH 14/21] staging: lustre: fix assorted checkpatch errors

> -Original Message- > Thanks for the review. Yes, you are correct. > I had seen that end_dirent was initialized to NULL, and let myself > believe that would make the transformation safe. > In fact, that initialization to NULL is pointless as it is never used. > > Maybe this would be bett

Re: [PATCH] mmc: dw_mmc-k3: Fix out-of-bounds access through DT alias

On Tue, Feb 20, 2018 at 10:03 AM, Geert Uytterhoeven wrote: > The hs_timing_cfg[] array is indexed using a value derived from the > "mshcN" alias in DT, which may lead to an out-of-bounds access. > > Fix this by adding a range check. > > Fixes: 7d92895208a008a2 ("mmc: dw_mmc-k3: Fix out-of-bounds

Re: [PATCH 4/9] serial: mxs-auart: Fix out-of-bounds access through DT alias

On Tue, Feb 20, 2018 at 10:40 AM, Geert Uytterhoeven wrote: > The auart_port[] array is indexed using a value derived from the > "serialN" alias in DT, which may lead to an out-of-bounds access. > > Fix this by adding a range check. > > Fixes: cabf23e7aa00b145 ("serial: mxs-auart: Fix out-of-bound

Re: [PATCH 2/9] serial: fsl_lpuart: Fix out-of-bounds access through DT alias

On Tue, Feb 20, 2018 at 10:40 AM, Geert Uytterhoeven wrote: > The lpuart_ports[] array is indexed using a value derived from the > "serialN" alias in DT, which may lead to an out-of-bounds access. > > Fix this by adding a range check. > > Fixes: 970416c691dc68b5 ("serial: fsl_lpuart: Fix out-of-bo

Re: [PATCH 5/9] serial: pxa: Fix out-of-bounds access through DT alias

On Tue, Feb 20, 2018 at 10:40 AM, Geert Uytterhoeven wrote: > The serial_pxa_ports[] array is indexed using a value derived from the > "serialN" alias in DT, which may lead to an out-of-bounds access. > > Fix this by adding a range check. > > Fixes: c8dcdc77298dde67 ("serial: pxa: Fix out-of-bound

Re: [PATCH 6/9] serial: samsung: Fix out-of-bounds access through DT alias

On Tue, Feb 20, 2018 at 10:40 AM, Geert Uytterhoeven wrote: > The s3c24xx_serial_ports[] array is indexed using a value derived from > the "serialN" alias in DT, which may lead to an out-of-bounds access. > > Fix this by adding a range check. > > Note that the array size is defined by a Kconfig sy

Re: [PATCH 7/9] serial: sh-sci: Fix out-of-bounds access through DT alias

On Tue, Feb 20, 2018 at 10:40 AM, Geert Uytterhoeven wrote: > The sci_ports[] array is indexed using a value derived from the > "serialN" alias in DT, which may lead to an out-of-bounds access. > > Fix this by adding a range check. > > Note that the array size is defined by a Kconfig symbol > (CON

Re: [PATCH 8/9] serial: sirf: Fix out-of-bounds access through DT alias

On Tue, Feb 20, 2018 at 10:40 AM, Geert Uytterhoeven wrote: > The sirf_ports[] array is indexed using a value derived from the > "serialN" alias in DT, which may lead to an out-of-bounds access. > > Fix this by adding a range check. > > Fixes: 66c7ab1120585d18 ("serial: sirf: Fix out-of-bounds acc

Re: [PATCH] usb: host: ehci-platform: add support for optional external vbus supply

Hi, On 02/20/2018 10:27 AM, Roger Quadros wrote: > Hi, > > On 20/02/18 11:11, Amelie Delaunay wrote: >> On some boards, especially when vbus supply requires large current, >> and the charge pump on the PHY isn't enough, an external vbus power switch >> may be used. >> Add support for this optiona

Appending firmware/hardware dump to vmcore during kernel panic

Hi all, We have a requirement to collect firmware/hardware state of the underlying NIC during kernel panic. We are doing this in cxgb4 driver, using panic notifier list [1]. cxgb4 registers a callback function to the panic notifier list, which gets invoked during kernel panic. In the callback fu

Re: [PATCH] PCI: Add quirk for Cavium Thunder-X2 PCIe erratum #173

On Tuesday, February 20, 2018 2:54:33 AM CET Lukas Wunner wrote: > On Mon, Feb 19, 2018 at 12:21:56PM +0100, Rafael J. Wysocki wrote: > > On Friday, February 16, 2018 9:34:34 PM CET Bjorn Helgaas wrote: > > > On Fri, Feb 16, 2018 at 01:40:37PM +0100, Rafael J. Wysocki wrote: > > > > On Friday, Febr

Re: [PATCH v4] rtc: isl12026: Add driver.

Hi, On 16/02/2018 at 11:44:15 -0800, David Daney wrote: > The ISL12026 is a combination RTC and EEPROM device with I2C > interface. The standard RTC driver interface is provided. The EEPROM > is accessed via the NVMEM interface via the "eeprom0" directory in the > sysfs entry for the device. >

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

>>> On 20.02.18 at 11:17, wrote: > I assume the Xen fix got merged meanwhile? Yes (that's the commit I've referred to in an earlier reply). Jan

[PATCH] cpufreq: scpi: invoke frequency-invariance setter function

Commit 343a8d17fa8d ("cpufreq: scpi: remove arm_big_little dependency") changed the cpufreq driver on juno from arm_big_little to scpi. The scpi set_target function does not call the frequency-invariance setter function arch_set_freq_scale() like the arm_big_little set_target function does. As a r

Re: [PATCH 3/3] Kconfig: add a default allrandom.config

On Tue, Feb 20, 2018 at 10:16 AM, Masahiro Yamada wrote: > 2018-02-17 6:41 GMT+09:00 Arnd Bergmann : >> Building randconfig kernels frequently leads to build errors from >> drivers that have additional build dependencies, or that we don't >> want to build for compile-testing for some other reason.

Re: [PATCH v2] xhci: Fix front USB ports on ASUS PRIME B350M-A

> On 20 Feb 2018, at 4:24 PM, Mathias Nyman > wrote: > > Hi > > On 19.02.2018 21:06, Kai-Heng Feng wrote: >> When a USB device gets plugged on ASUS PRIME B350M-A's front ports, the >> xHC stops working: >> [ 549.114587] xhci_hcd :02:00.0: WARN: xHC CMD_RUN timeout >> [ 549.114608] suspe

[PATCH] ACPI / CPPC: Update all pr_(debug/err) messages to log the susbspace id

CPPC dirver is aware of multiple PCC subspace IDs. Enhance the debug and error messages in the driver to print the subspace id. In case of error it will be helpful to find which particular subspace is failing. Signed-off-by: George Cherian --- drivers/acpi/cppc_acpi.c | 27 --

Re: [PATCH] PM / wakeirq: Add wakeup name to dedicated wake irqs

On Friday, February 16, 2018 3:52:22 PM CET Andy Shevchenko wrote: > On Fri, Feb 16, 2018 at 12:54 PM, Rafael J. Wysocki wrote: > > On Fri, Feb 16, 2018 at 11:39 AM, Andy Shevchenko > > wrote: > >> On Fri, Feb 16, 2018 at 11:14 AM, Rafael J. Wysocki > >> wrote: > >>> On Wed, Feb 14, 2018 at 12:

Re: [PATCH] drm/simple_kms_helper: Fix NULL pointer dereference with no active CRTC

On Mon, Feb 19, 2018 at 04:58:43PM +0200, Oleksandr Andrushchenko wrote: > On 02/19/2018 04:30 PM, Daniel Vetter wrote: > > On Tue, Feb 13, 2018 at 10:44:16AM +0200, Oleksandr Andrushchenko wrote: > > > From: Oleksandr Andrushchenko > > > > > > It is possible that drm_simple_kms_plane_atomic_chec

Re: [PATCH v3 2/4] x86/speculation: Support "Enhanced IBRS" on future CPUs

On Tue, 2018-02-20 at 11:42 +0100, Thomas Gleixner wrote: > > > > However, Paolo is very insistent that taking the trap every time is > > > actually a lot *slower* than really frobbing IBRS on certain > > > microarchitectures, so my hand-waving "pfft, what did they expect?" is > > > not acceptab

Re: [PATCH v3 2/4] x86/speculation: Support "Enhanced IBRS" on future CPUs

On 19/02/2018 11:50, David Woodhouse wrote: > Cope with this by trapping and emulating *all* access to SPEC_CTRL from > KVM guests when the IBRS_ALL feature is present, so it can never be > turned off. Guests who see IBRS_ALL should never do anything except > turn it on at boot anyway. And if they

Re: [PATCH 9/9] serial: xuartps: Fix out-of-bounds access through DT alias

On 20.2.2018 11:38, Geert Uytterhoeven wrote: > Hi Michal, > > On Tue, Feb 20, 2018 at 11:22 AM, Michal Simek > wrote: >> On 20.2.2018 10:40, Geert Uytterhoeven wrote: >>> The cdns_uart_port[] array is indexed using a value derived from the >>> "serialN" alias in DT, which may lead to an out-of-

Re: [PATCH v3 2/4] x86/speculation: Support "Enhanced IBRS" on future CPUs

On 20/02/2018 12:22, David Woodhouse wrote: However, Paolo is very insistent that taking the trap every time is actually a lot *slower* than really frobbing IBRS on certain microarchitectures, so my hand-waving "pfft, what did they expect?" is not acceptable.   Which I

Re: [PATCH 16/18] crypto: talitos - do hw_context DMA mapping outside the requests

On 2/20/2018 12:34 PM, Herbert Xu wrote: > On Mon, Feb 19, 2018 at 01:16:30PM +, Horia Geantă wrote: >> >>> And what about ALGIF path from user space ? >>> What if the user never calls the last sendmsg() which will call >>> hash_finup() ? >>> >> User is expected to follow the rules of the cryp

Re: [PATCH 1/3] locking/ww_mutex: cleanup lock->ctx usage in amdgpu

On Tue, Feb 20, 2018 at 10:43:48AM +0100, Christian König wrote: > Am 19.02.2018 um 17:43 schrieb Daniel Vetter: > > On Mon, Feb 19, 2018 at 05:29:46PM +0100, Christian König wrote: > > > [SNIP] > > > Well that is not a problem at all. See we don't nest trylock with normal > > > lock acquiring, cau

[PATCH] kconfig: Don't leak choice names during parsing

The named choice is not used in the kernel tree, but if it were used, it would not be freed. The intention of the named choice can be seen in the log of commit 5a1aa8a1aff6 ("kconfig: add named choice group"). There is room for argument if this is useful in practice, but anyway I am fixing the me

[PATCH v2] tpm: use kmemdup() to copy the event log

Replaced kmalloc() + memcpy() in tpm_eventlog_efi.c and tpm_eventlog_of.c. Signed-off-by: Jarkko Sakkinen --- v2: update also tpm_eventlog_of.c drivers/char/tpm/tpm_eventlog_efi.c | 3 +-- drivers/char/tpm/tpm_eventlog_of.c | 5 + 2 files changed, 2 insertions(+), 6 deletions(-) diff --git

Re: [PATCH 2/2] x86/speculation: Support "Enhanced IBRS" on future CPUs

On 20/02/2018 01:00, Van De Ven, Arjan wrote: >>> the guest is not the problem; guests obviously will already honor >>> if Enhanced IBRS is enumerated. The problem is mixed migration >>> pools where the hypervisor >>> may need to decide to not pass this enumeration through to the >>> guest. >> For

[PATCH v2 2/2] mfd: arizona: Update DT doc to support more standard reset binding

Signed-off-by: Charles Keepax --- Changes since v1: - Drop vendor prefix from new binding since it is a standard property. Thanks, Charles Documentation/devicetree/bindings/mfd/arizona.txt | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindin

Re: [PATCH] regulator: core: Handle PM_SUSPEND_TO_IDLE suspend_state_t

On Mon, Feb 19, 2018 at 09:59:13PM +0100, Hans de Goede wrote: > On 19-02-18 12:34, Mark Brown wrote: > There are multiple callers of regulator_get_suspend_state() in > drivers/regulator/core.c, I assume you refer to this commit: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

[PATCH] PCMCIA / PM: Combine system resume callbacks

From: Rafael J. Wysocki There is a problem with PCMCIA system resume callbacks with respect to suspend-to-idle in which the ->suspend_noirq() callback may be invoked after the ->resume_noirq() one without resuming the system entirely in some cases. This doesn't work for PCMCIA because of the lac

[PATCH v2] usb: core: introduce per-port over-current counters

From: Richard Leitner For some userspace applications information on the number of over-current conditions at specific USB hub ports is relevant. In our case we have a series of USB hardware (using the cp210x driver) which communicates using a proprietary protocol. These devices sometimes trigge

[PATCH 2/2] ASoC: ak4458: Sort headers alphabetically

Keep headers sorted alphabetically. Signed-off-by: Cosmin-Gabriel Samoila --- sound/soc/codecs/ak4458.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/sound/soc/codecs/ak4458.c b/sound/soc/codecs/ak4458.c index 8a49dd2..31ec0ba 100644 --- a/sound/soc/codecs/ak4458

[PATCH 1/2] ASoC: ak4458: Modify SPDX license format

Modify SPDX comment style to match the rules. Since the original code had a GPL-2.0 license and SPDX is compatible with GPL-2.0+, we also modified the MODULE_LICENSE. Signed-off-by: Cosmin-Gabriel Samoila --- sound/soc/codecs/ak4458.c | 13 ++--- sound/soc/codecs/ak4458.h | 2 +- 2 file

[PATCH 0/2] Fix coding style issues in AK4458 DAC

Modify SPDX license comment style and sort headers alphabetically. Cosmin-Gabriel Samoila (2): ASoC: ak4458: Modify SPDX license format ASoC: ak4458: Sort headers alphabetically sound/soc/codecs/ak4458.c | 23 +++ sound/soc/codecs/ak4458.h | 2 +- 2 files changed, 12 ins

Re: [PATCH v2] usb: core: introduce per-port over-current counters

Hi, Richard Leitner writes: > From: Richard Leitner > > For some userspace applications information on the number of > over-current conditions at specific USB hub ports is relevant. > > In our case we have a series of USB hardware (using the cp210x driver) > which communicates using a proprieta

[4.4-stable 00/22] patches for 'randconfig'

Like the earlier series of randconfig build fixes for 4.9, this is the equivalent for 4.4. Again, most of it is for harmless warnings, but there are also fixes for excessive stack consumption that can be possibly dangerous, and the 'genksyms' segfault fix is now needed to build the backported 'retp

[4.4-stable 01/22] gpio: xgene: mark PM functions as __maybe_unused

When CONFIG_PM_SLEEP is disabled, we get a warning about unused functions: drivers/gpio/gpio-xgene.c:155:12: warning: 'xgene_gpio_resume' defined but not used [-Wunused-function] static int xgene_gpio_resume(struct device *dev) ^ drivers/gpio/gpio-xgene.c:142:12: warn

[4.4-stable 07/22] usb: phy: msm add regulator dependency

On linux-4.4 and linux-4.9 we get a warning about an array that is never initialized when CONFIG_REGULATOR is disabled: drivers/usb/phy/phy-msm-usb.c: In function 'msm_otg_probe': drivers/usb/phy/phy-msm-usb.c:1911:14: error: 'regs[0].consumer' may be used uninitialized in this function [-Werror=

[4.4-stable 02/22] Revert "power: bq27xxx_battery: Remove unneeded dependency in Kconfig"

This reverts commit 6bd03ce3c12a22d86f59070f1da15aaa2bde8a51, it was applied in error and cuased this link failure drivers/built-in.o: In function `bq27xxx_battery_i2c_read': core.c:(.text+0xa6da8): undefined reference to `i2c_transfer' drivers/built-in.o: In function `bq27xxx_battery_init': core.

[4.4-stable 08/22] ncr5380: shut up gcc indentation warning

gcc-6 and higher warn about the way some loops are written in the ncr5380 driver: drivers/scsi/g_NCR5380.c: In function 'generic_NCR5380_pread': drivers/scsi/g_NCR5380.c:541:3: error: this 'while' clause does not guard... [-Werror=misleading-indentation] while (NCR5380_read(C400_CONTROL_STATUS

[4.4-stable 04/22] isdn: sc: work around type mismatch warning

This driver shows warnings on many architectures: drivers/isdn/sc/init.c: In function 'identify_board': drivers/isdn/sc/init.c:484:2: error: passing argument 1 of 'readl' makes pointer from integer without a cast [-Werror] In newer kernels, it was completely removed, but for the 4.4-stable serie

[4.4-stable 05/22] binfmt_elf: compat: avoid unused function warning

When CONFIG_ELF_CORE is disabled, we get a harmless warning in the compat version of binfmt_elf: fs/compat_binfmt_elf.c:58:13: error: 'cputime_to_compat_timeval' defined but not used [-Werror=unused-function] This was addressed in mainline Linux as part of a larger rework with commit cd19c364b31

[4.4-stable 06/22] idle: i7300: add PCI dependency

GCC correctly points out an uninitialized variable use when CONFIG_PCI is disabled. drivers/idle/i7300_idle.c: In function 'i7300_idle_notifier': include/asm-generic/bug.h:119:5: error: 'got_ctl' may be used uninitialized in this function [-Werror=maybe-uninitialized] if (unlikely(__ret_warn_o

[4.4-stable 03/22] power: bq27xxx_battery: mark some symbols __maybe_unused

Without the I2C driver, we get a few warnings: drivers/power/bq27xxx_battery.c:288:12: error: 'bq27xxx_regs' defined but not used [-Werror=unused-variable] static u8 *bq27xxx_regs[] = { ^ drivers/power/bq27xxx_battery.c:994:12: error: 'bq27xxx_powersupply_init' defined but not used

[4.4-stable 12/22] virtio_balloon: prevent uninitialized variable use

commit f0bb2d50dfcc519f06f901aac88502be6ff1df2c upstream. The latest gcc-7.0.1 snapshot reports a new warning: virtio/virtio_balloon.c: In function 'update_balloon_stats': virtio/virtio_balloon.c:258:26: error: 'events[2]' is used uninitialized in this function [-Werror=uninitialized] virtio/vir

[4.4-stable 13/22] dell-wmi, dell-laptop: depends DMI

From: Andy Lutomirski commit a570af4850043260b87fb1b8aa27a4484e648878 upstream. dell-wmi and dell-laptop will compile but won't work right if DMI isn't selected. Signed-off-by: Andy Lutomirski Acked-by: Pali Rohár [arnd: Use depends instead of selects to avoid recursive dependencies] Signed-o

[4.4-stable 10/22] ASoC: Intel: Kconfig: fix build when ACPI is not enabled

From: Vinod Koul commit 3493d4a86457c7de9f1e602b4267c9b0f9ec1c9f upstream. Randy reported following error when ACPI is not enabled: warning: (SND_SOC_INTEL_BYTCR_RT5640_MACH && SND_SOC_INTEL_BYTCR_RT5651_MACH && SND_SOC_INTEL_CHT_BSW_RT5672_MACH && SND_SOC_INTEL_CHT_BSW_RT5645_MACH && SND_SOC_I

[4.4-stable 14/22] genksyms: Fix segfault with invalid declarations

From: Michal Marek commit d920f7c6628c63a390009c237fb80a203c2e400a upstream. Do not try to recover too early and segfault when parsing invalid declarations such as echo 'int (int);' | scripts/genksyms/genksyms echo 'int a, (int);' | scripts/genksyms/genksyms echo 'extern void *__inline_memcpy((

[4.4-stable 20/22] ncpfs: fix unused variable warning

From: Miklos Szeredi commit 9a232de4999666b2e8ea6775b2b0e3e4feb09b7a upstream. Without CONFIG_NCPFS_NLS the following warning is seen: fs/ncpfs/dir.c: In function 'ncp_hash_dentry': fs/ncpfs/dir.c:136:23: warning: unused variable 'sb' [-Wunused-variable] struct super_block *sb = dentry->d_sb

[PATCH v4 1/7] firmware: tegra: Simplify channel management

The Tegra194 BPMP only implements 5 channels (4 to BPMP, 1 to CCPLEX), and they are not placed contiguously in memory. The current channel management in the BPMP driver does not support this. Simplify and refactor the channel management such that only one atomic transmit channel and one receive ch

[PATCH v4 0/7] Initial support for NVIDIA Tegra194

Hello everyone, this series adds initial support for the NVIDIA Tegra194 "Xavier" system-on-chip. Initially UART, I2C, SDMMC, as well as the PMIC are supported, allowing booting to a console. The changes consist almost completely of the new device trees, however some fixes are required in the BPM

[PATCH v4 7/7] arm64: tegra: Add device tree for the Tegra194 P2972-0000 board

Add device tree files for the Tegra194 P2972- development board. The board consists of the P2888 compute module and the P2822 baseboard. Signed-off-by: Mikko Perttunen --- arch/arm64/boot/dts/nvidia/Makefile| 1 + arch/arm64/boot/dts/nvidia/tegra194-p2888.dtsi | 248 +++

[PATCH v4 3/7] soc/tegra: pmc: Add Tegra194 compatibility string

The Tegra194 PMC is mostly compatible with Tegra186, including in all currently supported features. As such, add a new compatibility string but point to the existing Tegra186 SoC data for now. Signed-off-by: Mikko Perttunen --- drivers/soc/tegra/pmc.c | 1 + 1 file changed, 1 insertion(+) diff

[4.4-stable 19/22] net: hp100: remove unnecessary #ifdefs

commit 747a11279a442b913a57bf38934879babab3b58b upstream. Building the hp100 ethernet driver causes warnings when both the PCI and EISA drivers are disabled: ethernet/hp/hp100.c: In function 'hp100_module_init': ethernet/hp/hp100.c:3047:2: warning: label 'out3' defined but not used [-Wunused-lab

[PATCH v4 5/7] dt-bindings: tegra: Add documentation for nvidia,tegra194-pmc

The Tegra194 power management controller has one additional register aperture to be specified in the device tree node. Signed-off-by: Mikko Perttunen Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-pmc.txt | 2 ++ 1 file changed, 2 insertions(+) diff --

[4.4-stable 15/22] perf/x86: Shut up false-positive -Wmaybe-uninitialized warning

commit 11d8b05855f3749bcb6c57e2c4052921b9605c77 upstream. The intialization function checks for various failure scenarios, but unfortunately the compiler gets a little confused about the possible combinations, leading to a false-positive build warning when -Wmaybe-uninitialized is set: arch/x86

[PATCH v4 6/7] arm64: tegra: Add Tegra194 chip device tree

Add the chip-level device tree, including binding headers, for the NVIDIA Tegra194 "Xavier" system-on-chip. Only a small subset of devices are initially available, enough to boot to UART console. Signed-off-by: Mikko Perttunen --- Notes: v4: - fixed copyright headers according to license

[4.4-stable 18/22] x86/microcode/AMD: Change load_microcode_amd()'s param to bool to fix preemptibility bug

From: Borislav Petkov commit dac6ca243c4c49a9ca7507d3d66140ebfac8b04b upstream. With CONFIG_DEBUG_PREEMPT enabled, I get: BUG: using smp_processor_id() in preemptible [] code: swapper/0/1 caller is debug_smp_processor_id CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.12.0-rc2+ #2 C

[PATCH v4 4/7] dt-bindings: tegra: Add missing chips and NVIDIA boards

Add compatibility strings for supported but undocumented Tegra chips (Tegra114/124/132/210/186/194) and reference boards. Signed-off-by: Mikko Perttunen Reviewed-by: Rob Herring --- Notes: v2: - add patch Documentation/devicetree/bindings/arm/tegra.txt | 16 1 file ch

[4.4-stable 22/22] kasan: rework Kconfig settings

commit e7c52b84fb18f08ce49b6067ae6285aca79084a8 upstream. We get a lot of very large stack frames using gcc-7.0.1 with the default -fsanitize-address-use-after-scope --param asan-stack=1 options, which can easily cause an overflow of the kernel stack, e.g. drivers/gpu/drm/i915/gvt/handlers.c:24

[PATCH v4 2/7] soc/tegra: Add Tegra194 SoC configuration option

Add the configuration option to enable support for the Tegra194 system-on-chip, and enable it by default in the arm64 defconfig. Signed-off-by: Mikko Perttunen --- arch/arm64/configs/defconfig | 1 + drivers/soc/tegra/Kconfig| 10 ++ 2 files changed, 11 insertions(+) diff --git a/a

[4.4-stable 21/22] drm/gma500: remove helper function

From: Sudip Mukherjee commit db9b60400f9253c25ae639797df2d0ff7a35d9d8 upstream. We were getting build warning about: drivers/gpu/drm/gma500/mdfld_dsi_output.c:407:2: warning: initialization from incompatible pointer type The callback to dpms was pointing to a helper function which had a

[4.4-stable 16/22] dmaengine: zx: fix build warning

From: Jun Nie commit 067fdeb2f391bfa071f741a2b3eb74b8ff3785cd upstream. Fix build warning that related to PAGE_SIZE. The maximum DMA length has nothing to do with PAGE_SIZE, just use a fix number for the definition. drivers/dma/zx_dma.c: In function 'zx_dma_prep_memcpy': drivers/dma/zx_dma.c:52

[4.4-stable 17/22] cw1200: fix bogus maybe-uninitialized warning

commit 7fc1503c906f0fac62d3506a6e993e49fb996248 upstream. On x86, the cw1200 driver produces a rather silly warning about the possible use of the 'ret' variable without an initialization presumably after being confused by the architecture specific definition of WARN_ON: drivers/net/wireless/st/cw

[4.4-stable 09/22] ARM: tegra: select USB_ULPI from EHCI rather than platform

commit a262e87ff354f12447bb6268bd63edf7ba1c20e0 upstream. For historic reasons, the tegra platform selects USB_ULPI from architecture code, but that hasn't really made sense for a long time, as the only user of that code is the Tegra EHCI driver that has its own Kconfig symbol. This removes the '

[4.4-stable 11/22] netlink: fix nla_put_{u8,u16,u32} for KASAN

commit b4391db42308c9940944b5d7be5ca4b78fb88dd0 upstream. When CONFIG_KASAN is enabled, the "--param asan-stack=1" causes rather large stack frames in some functions. This goes unnoticed normally because CONFIG_FRAME_WARN is disabled with CONFIG_KASAN by default as of commit 3f181b4d8652 ("lib/Kco

Re: [PATCH 2/2] ASoC: max9759: Add Amplifier Driver

On Mon, Feb 19, 2018 at 02:45:58PM +0100, Neil Armstrong wrote: > +++ b/sound/soc/codecs/max9759.c > @@ -0,0 +1,207 @@ > +// SPDX-Licence-Identifier: GPL-2.0 > +/* > + * MAX9759 Amplifier Driver > + * Please don't mix C and C++ style comments like this, make it all a C++ comment - it looks more i

<    3   4   5   6   7   8   9   >