Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Tue, Jun 21, 2016 at 10:17:38PM +0200, Julia Lawall wrote: > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > Coccinelle has had parmap support since 1.0.2, this means > > it supports --jobs, enabling built-in multithreaded functionality, > > instead of needing one to script it out.

Re: linux-next: Tree for Jun 21

On Tue, Jun 21, 2016 at 02:36:34PM -0400, Chris Metcalf wrote: > On 6/21/2016 2:28 PM, Peter Zijlstra wrote: > >I had to s/__atomic_fetch/__atomic32_fetch/ to avoid a namespace clash > >with the builtin C11 atomic primitives. > > > >You want me to rename them all to regain consistent naming? > >

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Tue, Jun 21, 2016 at 10:17:38PM +0200, Julia Lawall wrote: > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > Coccinelle has had parmap support since 1.0.2, this means > > it supports --jobs, enabling built-in multithreaded functionality, > > instead of needing one to script it out.

Re: linux-next: Tree for Jun 21

On Tue, Jun 21, 2016 at 02:36:34PM -0400, Chris Metcalf wrote: > On 6/21/2016 2:28 PM, Peter Zijlstra wrote: > >I had to s/__atomic_fetch/__atomic32_fetch/ to avoid a namespace clash > >with the builtin C11 atomic primitives. > > > >You want me to rename them all to regain consistent naming? > >

Re: [PATCH v3 1/8] coccicheck: move spatch binary check up

Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit : This has no functional changes. This is being done to enable us to later use spatch binary for some flag checking for certain features early on. Signed-off-by: Luis R. Rodriguez Acked-by: Nicolas Palix

Re: [PATCH v3 1/8] coccicheck: move spatch binary check up

Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit : This has no functional changes. This is being done to enable us to later use spatch binary for some flag checking for certain features early on. Signed-off-by: Luis R. Rodriguez Acked-by: Nicolas Palix --- scripts/coccicheck | 10 +-

Re: [PATCH v3 8/8] scripts/coccinelle: require coccinelle >= 1.0.4 on device_node_continue.cocci

On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > Make use of the new Requires: tag to be able to specify coccinelle binary > version requirements. The cocci file device_node_continue.cocci requires at > least coccinelle 1.0.4. > > Signed-off-by: Luis R. Rodriguez Acked-by:

Re: [PATCH v3 8/8] scripts/coccinelle: require coccinelle >= 1.0.4 on device_node_continue.cocci

On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > Make use of the new Requires: tag to be able to specify coccinelle binary > version requirements. The cocci file device_node_continue.cocci requires at > least coccinelle 1.0.4. > > Signed-off-by: Luis R. Rodriguez Acked-by: Julia Lawall >

Re: [PATCH 1/3] staging: lowmemorykiller: change lowmem_adj to lowmem_score_adj

On Tue, 21 Jun 2016, Ganesh Mahendran wrote: > om_adj is deprecated, and in lowmemorykiller module, we use score adj > to do the comparing. > --- > oom_score_adj = p->signal->oom_score_adj; > if (oom_score_adj < min_score_adj) { >

Re: [PATCH 1/3] staging: lowmemorykiller: change lowmem_adj to lowmem_score_adj

On Tue, 21 Jun 2016, Ganesh Mahendran wrote: > om_adj is deprecated, and in lowmemorykiller module, we use score adj > to do the comparing. > --- > oom_score_adj = p->signal->oom_score_adj; > if (oom_score_adj < min_score_adj) { >

Re: Documenting ptrace access mode checking

On Tue, Jun 21, 2016 at 12:55 PM, Eric W. Biederman wrote: > > Adding Oleg just because he seems to do most of the ptrace related > maintenance these days. > > "Michael Kerrisk (man-pages)" writes: > >> Hi Jann, Stephen, et al. >> >> Jann, since you

Re: [PATCH 2/2] ipc/sem: sem_lock with hysteresis

On Sat, 18 Jun 2016, Manfred Spraul wrote: sysv sem has two lock modes: One with per-semaphore locks, one lock mode with a single big lock for the whole array. When switching from the per-semaphore locks to the big lock, all per-semaphore locks must be scanned for ongoing operations. The patch

Re: Documenting ptrace access mode checking

On Tue, Jun 21, 2016 at 12:55 PM, Eric W. Biederman wrote: > > Adding Oleg just because he seems to do most of the ptrace related > maintenance these days. > > "Michael Kerrisk (man-pages)" writes: > >> Hi Jann, Stephen, et al. >> >> Jann, since you recently committed a patch in this area, and

Re: [PATCH 2/2] ipc/sem: sem_lock with hysteresis

On Sat, 18 Jun 2016, Manfred Spraul wrote: sysv sem has two lock modes: One with per-semaphore locks, one lock mode with a single big lock for the whole array. When switching from the per-semaphore locks to the big lock, all per-semaphore locks must be scanned for ongoing operations. The patch

Re: [PATCH 10/10] perf script: Add stackcollapse.py script

Em Tue, Jun 21, 2016 at 11:36:10AM -0700, Brendan Gregg escreveu: > On Mon, Jun 20, 2016 at 3:23 PM, Arnaldo Carvalho de Melo > wrote: > > From: Paolo Bonzini > > > > Add stackcollapse.py script as an example of parsing call chains, and > > also of using

Re: [PATCH 10/10] perf script: Add stackcollapse.py script

Em Tue, Jun 21, 2016 at 11:36:10AM -0700, Brendan Gregg escreveu: > On Mon, Jun 20, 2016 at 3:23 PM, Arnaldo Carvalho de Melo > wrote: > > From: Paolo Bonzini > > > > Add stackcollapse.py script as an example of parsing call chains, and > > also of using optparse to access command line options.

Re: [PATCHv3 1/2] usb: USB Type-C connector class

On Tue, 2016-06-21 at 17:51 +0300, Heikki Krogerus wrote: > +What: /sys/class/typec//supported_data_roles > +Data: June 2016 > +Contact: Heikki Krogerus > +Description: > + Lists the USB data roles, host or device, the port is

Re: [PATCH v3 5/8] scripts: add Linux .cocciconfig for coccinelle

On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > Help Coccinelle when used against Linux with a set of sensible defaults > options for Linux. This hints to coccinelle git can be used for 'git grep' > queries over coccigrep. A timeout of 200 seconds should suffice for now. > > If you use idutils

Re: [PATCHv3 1/2] usb: USB Type-C connector class

On Tue, 2016-06-21 at 17:51 +0300, Heikki Krogerus wrote: > +What: /sys/class/typec//supported_data_roles > +Data: June 2016 > +Contact: Heikki Krogerus > +Description: > + Lists the USB data roles, host or device, the port is > capable > + of

Re: [PATCH v3 5/8] scripts: add Linux .cocciconfig for coccinelle

On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > Help Coccinelle when used against Linux with a set of sensible defaults > options for Linux. This hints to coccinelle git can be used for 'git grep' > queries over coccigrep. A timeout of 200 seconds should suffice for now. > > If you use idutils

Re: [PATCH v3 0/8] coccicheck: modernize

is always at the end of options > o rebases on top of Deepa Dinamani's patch > "coccicheck: Allow for overriding spatch flags", under the assumption this > is already merged. I don't see it on linux-next but I do think Michal > has merged already onto his tre

Re: [PATCH v3 0/8] coccicheck: modernize

is always at the end of options > o rebases on top of Deepa Dinamani's patch > "coccicheck: Allow for overriding spatch flags", under the assumption this > is already merged. I don't see it on linux-next but I do think Michal > has merged already onto his tre

Re: [PATCH 2/3] staging: lowmemorykiller: count anon pages only when we have swap devices

On Tue, 21 Jun 2016, Ganesh Mahendran wrote: > lowmem_count() should only count anon pages when we have swap device. > Why? > Signed-off-by: Ganesh Mahendran > --- > drivers/staging/android/lowmemorykiller.c | 12 > 1 file changed, 8 insertions(+), 4

Re: [PATCH 2/3] staging: lowmemorykiller: count anon pages only when we have swap devices

On Tue, 21 Jun 2016, Ganesh Mahendran wrote: > lowmem_count() should only count anon pages when we have swap device. > Why? > Signed-off-by: Ganesh Mahendran > --- > drivers/staging/android/lowmemorykiller.c | 12 > 1 file changed, 8 insertions(+), 4 deletions(-) > > diff --git

Re: [PATCH v3 00/13] Virtually mapped stacks with guard pages (x86, core)

On Tue, Jun 21, 2016 at 12:47 PM, Andy Lutomirski wrote: > On Tue, Jun 21, 2016 at 12:47 PM, Arnd Bergmann wrote: >> On Tuesday, June 21, 2016 10:16:21 AM CEST Kees Cook wrote: >>> On Tue, Jun 21, 2016 at 2:24 AM, Arnd Bergmann wrote: >>> > On

Re: [PATCH v3 00/13] Virtually mapped stacks with guard pages (x86, core)

On Tue, Jun 21, 2016 at 12:47 PM, Andy Lutomirski wrote: > On Tue, Jun 21, 2016 at 12:47 PM, Arnd Bergmann wrote: >> On Tuesday, June 21, 2016 10:16:21 AM CEST Kees Cook wrote: >>> On Tue, Jun 21, 2016 at 2:24 AM, Arnd Bergmann wrote: >>> > On Monday, June 20, 2016 4:43:30 PM CEST Andy

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > Coccinelle has had parmap support since 1.0.2, this means > it supports --jobs, enabling built-in multithreaded functionality, > instead of needing one to script it out. Just look for --jobs > in the help output to determine if this is supported.

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > Coccinelle has had parmap support since 1.0.2, this means > it supports --jobs, enabling built-in multithreaded functionality, > instead of needing one to script it out. Just look for --jobs > in the help output to determine if this is supported.

Re: [PATCH] arm64: mm: only initialize swiotlb when necessary

On Tuesday, June 21, 2016 5:06:25 PM CEST Catalin Marinas wrote: > On Wed, Jun 08, 2016 at 05:49:59PM +0200, Arnd Bergmann wrote: > > On Wednesday, June 8, 2016 1:08:29 PM CEST Catalin Marinas wrote: > > > On Wed, Jun 08, 2016 at 03:53:46PM +0800, Jisheng Zhang wrote: > > > > static int __init

Re: [PATCH] arm64: mm: only initialize swiotlb when necessary

On Tuesday, June 21, 2016 5:06:25 PM CEST Catalin Marinas wrote: > On Wed, Jun 08, 2016 at 05:49:59PM +0200, Arnd Bergmann wrote: > > On Wednesday, June 8, 2016 1:08:29 PM CEST Catalin Marinas wrote: > > > On Wed, Jun 08, 2016 at 03:53:46PM +0800, Jisheng Zhang wrote: > > > > static int __init

Re: [RFC][PATCH] arm: ubsan: select ARCH_HAS_UBSAN_SANITIZE_ALL

On Tuesday, June 21, 2016 7:34:03 PM CEST Andrey Ryabinin wrote: > > On 06/21/2016 02:44 PM, Arnd Bergmann wrote: > > On Tuesday, June 21, 2016 10:43:19 AM CEST Arnd Bergmann wrote: > >> On Tuesday, June 21, 2016 2:39:05 PM CEST Seung-Woo Kim wrote: > >>> To enable UBSAN on arm, this patch

Re: [RFC][PATCH] arm: ubsan: select ARCH_HAS_UBSAN_SANITIZE_ALL

On Tuesday, June 21, 2016 7:34:03 PM CEST Andrey Ryabinin wrote: > > On 06/21/2016 02:44 PM, Arnd Bergmann wrote: > > On Tuesday, June 21, 2016 10:43:19 AM CEST Arnd Bergmann wrote: > >> On Tuesday, June 21, 2016 2:39:05 PM CEST Seung-Woo Kim wrote: > >>> To enable UBSAN on arm, this patch

Re: [PATCH 02/48] ARM: at91: Document new TCB bindings

On Wed, Jun 15, 2016 at 09:29:55AM +0200, Boris Brezillon wrote: > On Tue, 14 Jun 2016 16:47:37 -0500 > Rob Herring wrote: > > > On Sat, Jun 11, 2016 at 12:03:05AM +0200, Alexandre Belloni wrote: > > > The current binding for the TCB is not flexible enough for some use cases > >

Re: [PATCH 02/48] ARM: at91: Document new TCB bindings

On Wed, Jun 15, 2016 at 09:29:55AM +0200, Boris Brezillon wrote: > On Tue, 14 Jun 2016 16:47:37 -0500 > Rob Herring wrote: > > > On Sat, Jun 11, 2016 at 12:03:05AM +0200, Alexandre Belloni wrote: > > > The current binding for the TCB is not flexible enough for some use cases > > > and prevents

Re: Documenting ptrace access mode checking

Adding Oleg just because he seems to do most of the ptrace related maintenance these days. "Michael Kerrisk (man-pages)" writes: > Hi Jann, Stephen, et al. > > Jann, since you recently committed a patch in this area, and Stephen, > since you committed 006ebb40d3d much

Re: Documenting ptrace access mode checking

Adding Oleg just because he seems to do most of the ptrace related maintenance these days. "Michael Kerrisk (man-pages)" writes: > Hi Jann, Stephen, et al. > > Jann, since you recently committed a patch in this area, and Stephen, > since you committed 006ebb40d3d much further back in time, I

[PATCH v5] Documentation: dt: reset: Add TI syscon reset binding

Add TI syscon reset controller binding. This will hook to the reset framework and use syscon/regmap to set reset bits. This allows reset control of individual SoC subsytems and devices with memory-mapped reset registers in a common register memory space. Signed-off-by: Andrew F. Davis

[PATCH v5] Documentation: dt: reset: Add TI syscon reset binding

Add TI syscon reset controller binding. This will hook to the reset framework and use syscon/regmap to set reset bits. This allows reset control of individual SoC subsytems and devices with memory-mapped reset registers in a common register memory space. Signed-off-by: Andrew F. Davis

Re: [PATCH] cgroup: Use lld instead of ld when printing pids controller events_limit

Hello, Added (s64) cast because atomic64 switches between l and ll. No idea why it doesn't just use s64. Thanks. -- 8< -- >From 9f6870dd9790dd87da1d0cf9e43e60113f3a278d Mon Sep 17 00:00:00 2001 From: Kenny Yu Date: Tue, 21 Jun 2016 11:55:35 -0700 Subject: [PATCH]

Re: [PATCH] cgroup: Use lld instead of ld when printing pids controller events_limit

Hello, Added (s64) cast because atomic64 switches between l and ll. No idea why it doesn't just use s64. Thanks. -- 8< -- >From 9f6870dd9790dd87da1d0cf9e43e60113f3a278d Mon Sep 17 00:00:00 2001 From: Kenny Yu Date: Tue, 21 Jun 2016 11:55:35 -0700 Subject: [PATCH] cgroup: Use lld

[PATCH v3 2/9] kexec_file: Generalize kexec_add_buffer.

Allow architectures to specify different memory walking functions for kexec_add_buffer. Intel uses iomem to track reserved memory ranges, but PowerPC uses the memblock subsystem. Signed-off-by: Thiago Jung Bauermann Cc: Eric Biederman Cc: Dave

[PATCH v3 4/9] powerpc: Factor out relocation code from module_64.c to elf_util_64.c.

The kexec_file_load system call needs to relocate the purgatory, so factor out the module relocation code so that it can be shared. This patch's purpose is to move the ELF relocation logic from apply_relocate_add to elf_util_64.c with as few changes as possible. The following changes were needed:

[PATCH v3 2/9] kexec_file: Generalize kexec_add_buffer.

Allow architectures to specify different memory walking functions for kexec_add_buffer. Intel uses iomem to track reserved memory ranges, but PowerPC uses the memblock subsystem. Signed-off-by: Thiago Jung Bauermann Cc: Eric Biederman Cc: Dave Young Cc: ke...@lists.infradead.org Cc:

[PATCH v3 4/9] powerpc: Factor out relocation code from module_64.c to elf_util_64.c.

The kexec_file_load system call needs to relocate the purgatory, so factor out the module relocation code so that it can be shared. This patch's purpose is to move the ELF relocation logic from apply_relocate_add to elf_util_64.c with as few changes as possible. The following changes were needed:

[PATCH v3 5/9] powerpc: Generalize elf64_apply_relocate_add.

When apply_relocate_add is called, modules are already loaded at their final location in memory so Elf64_Shdr.sh_addr can be used for accessing the section contents as well as the base address for relocations. This is not the case for kexec's purgatory, because it will only be copied to its final

[PATCH v3 7/9] powerpc: Implement kexec_file_load.

Adds the basic machinery needed by kexec_file_load. Signed-off-by: Josh Sklar Signed-off-by: Thiago Jung Bauermann Cc: ke...@lists.infradead.org Cc: linux-kernel@vger.kernel.org --- arch/powerpc/Kconfig | 13 +

[PATCH v3 5/9] powerpc: Generalize elf64_apply_relocate_add.

When apply_relocate_add is called, modules are already loaded at their final location in memory so Elf64_Shdr.sh_addr can be used for accessing the section contents as well as the base address for relocations. This is not the case for kexec's purgatory, because it will only be copied to its final

[PATCH v3 7/9] powerpc: Implement kexec_file_load.

Adds the basic machinery needed by kexec_file_load. Signed-off-by: Josh Sklar Signed-off-by: Thiago Jung Bauermann Cc: ke...@lists.infradead.org Cc: linux-kernel@vger.kernel.org --- arch/powerpc/Kconfig | 13 + arch/powerpc/include/asm/systbl.h | 1 +

RE: [PATCH 3/4] dell-wmi: Add information about other WMI event codes

> -Original Message- > From: Pali Rohár [mailto:pali.ro...@gmail.com] > Sent: Wednesday, June 15, 2016 2:51 PM > To: Limonciello, Mario > Cc: Gabriele Mazzotta ; mj...@srcf.ucam.org; > dvh...@infradead.org; ker...@kempniu.pl;

RE: [PATCH 3/4] dell-wmi: Add information about other WMI event codes

> -Original Message- > From: Pali Rohár [mailto:pali.ro...@gmail.com] > Sent: Wednesday, June 15, 2016 2:51 PM > To: Limonciello, Mario > Cc: Gabriele Mazzotta ; mj...@srcf.ucam.org; > dvh...@infradead.org; ker...@kempniu.pl; l...@kernel.org; > alex.h...@canonical.com;

Re: [kernel-hardening] Re: [PATCH v3 06/13] fork: Add generic vmalloced stack support

On Tuesday, June 21, 2016 2:32:28 PM CEST Rik van Riel wrote: > On Tue, 2016-06-21 at 10:13 -0700, Kees Cook wrote: > > On Tue, Jun 21, 2016 at 9:59 AM, Andy Lutomirski > > wrote: > > > > > > I'm tempted to explicitly disallow VM_NO_GUARD in the vmalloc > > > range. > > >

Re: [kernel-hardening] Re: [PATCH v3 06/13] fork: Add generic vmalloced stack support

On Tuesday, June 21, 2016 2:32:28 PM CEST Rik van Riel wrote: > On Tue, 2016-06-21 at 10:13 -0700, Kees Cook wrote: > > On Tue, Jun 21, 2016 at 9:59 AM, Andy Lutomirski > > wrote: > > > > > > I'm tempted to explicitly disallow VM_NO_GUARD in the vmalloc > > > range. > > > It has no in-tree users

[PATCH v3 1/9] kexec_file: Remove unused members from struct kexec_buf.

kexec_add_buffer uses kexec_buf.buffer and kexec_buf.bufsz to pass along its own arguments buffer and bufsz, but since they aren't used anywhere else, it's pointless. Signed-off-by: Thiago Jung Bauermann Cc: Eric Biederman Cc:

[PATCH v3 1/9] kexec_file: Remove unused members from struct kexec_buf.

kexec_add_buffer uses kexec_buf.buffer and kexec_buf.bufsz to pass along its own arguments buffer and bufsz, but since they aren't used anywhere else, it's pointless. Signed-off-by: Thiago Jung Bauermann Cc: Eric Biederman Cc: ke...@lists.infradead.org Cc: linux-kernel@vger.kernel.org Acked-by:

[PATCH v3 9/9] powerpc: Add purgatory for kexec_file_load implementation.

This purgatory implementation comes from kexec-tools, almost unchanged. The only changes were that the sha256_regions global variable was renamed to sha_regions to match what kexec_file_load expects, and to use the sha256.c file from x86's purgatory to avoid adding yet another SHA-256

[PATCH v3 0/9] kexec_file_load implementation for PowerPC

Hello, This patch series implements the kexec_file_load system call on PowerPC. This system call moves the reading of the kernel, initrd and the device tree from the userspace kexec tool to the kernel. This is needed if you want to do one or both of the following: 1. only allow loading of

[PATCH v3 3/9] kexec_file: Factor out kexec_locate_mem_hole from kexec_add_buffer.

kexec_locate_mem_hole will be used by the PowerPC kexec_file_load implementation to find free memory for the purgatory stack. Signed-off-by: Thiago Jung Bauermann Cc: Eric Biederman Cc: Dave Young Cc:

[PATCH v3 9/9] powerpc: Add purgatory for kexec_file_load implementation.

This purgatory implementation comes from kexec-tools, almost unchanged. The only changes were that the sha256_regions global variable was renamed to sha_regions to match what kexec_file_load expects, and to use the sha256.c file from x86's purgatory to avoid adding yet another SHA-256

[PATCH v3 0/9] kexec_file_load implementation for PowerPC

Hello, This patch series implements the kexec_file_load system call on PowerPC. This system call moves the reading of the kernel, initrd and the device tree from the userspace kexec tool to the kernel. This is needed if you want to do one or both of the following: 1. only allow loading of

[PATCH v3 3/9] kexec_file: Factor out kexec_locate_mem_hole from kexec_add_buffer.

kexec_locate_mem_hole will be used by the PowerPC kexec_file_load implementation to find free memory for the purgatory stack. Signed-off-by: Thiago Jung Bauermann Cc: Eric Biederman Cc: Dave Young Cc: ke...@lists.infradead.org Cc: linux-kernel@vger.kernel.org --- include/linux/kexec.h | 4

[PATCH v3 8/9] powerpc: Add support for loading ELF kernels with kexec_file_load.

This uses all the infrastructure built up by the previous patches in the series to load an ELF vmlinux file and an initrd. It uses the flattened device tree at initial_boot_params as a base and adjusts memory reservations and its /chosen node for the next kernel. elf64_apply_relocate_add was

[PATCH v3 6/9] powerpc: Add functions to read ELF files of any endianness.

A little endian kernel might need to kexec a big endian kernel (the opposite is less likely but could happen as well), so we can't just cast the buffer with the binary to ELF structs and use them as is done elsewhere. This patch adds functions which do byte-swapping as necessary when populating

[PATCH v3 8/9] powerpc: Add support for loading ELF kernels with kexec_file_load.

This uses all the infrastructure built up by the previous patches in the series to load an ELF vmlinux file and an initrd. It uses the flattened device tree at initial_boot_params as a base and adjusts memory reservations and its /chosen node for the next kernel. elf64_apply_relocate_add was

[PATCH v3 6/9] powerpc: Add functions to read ELF files of any endianness.

A little endian kernel might need to kexec a big endian kernel (the opposite is less likely but could happen as well), so we can't just cast the buffer with the binary to ELF structs and use them as is done elsewhere. This patch adds functions which do byte-swapping as necessary when populating

Re: [PATCH v3 00/13] Virtually mapped stacks with guard pages (x86, core)

On Tue, Jun 21, 2016 at 12:47 PM, Arnd Bergmann wrote: > On Tuesday, June 21, 2016 10:16:21 AM CEST Kees Cook wrote: >> On Tue, Jun 21, 2016 at 2:24 AM, Arnd Bergmann wrote: >> > On Monday, June 20, 2016 4:43:30 PM CEST Andy Lutomirski wrote: >> >> >> >> On my

Re: [PATCH v3 00/13] Virtually mapped stacks with guard pages (x86, core)

On Tue, Jun 21, 2016 at 12:47 PM, Arnd Bergmann wrote: > On Tuesday, June 21, 2016 10:16:21 AM CEST Kees Cook wrote: >> On Tue, Jun 21, 2016 at 2:24 AM, Arnd Bergmann wrote: >> > On Monday, June 20, 2016 4:43:30 PM CEST Andy Lutomirski wrote: >> >> >> >> On my laptop, this adds about 1.5µs of

Re: [RFC PATCHv2] usb: USB Type-C Connector Class

On Tue, 2016-06-21 at 06:24 -0700, Guenter Roeck wrote: > On 06/21/2016 06:08 AM, Oliver Neukum wrote: > > On Thu, 2016-05-19 at 15:44 +0300, Heikki Krogerus wrote: > >> The purpose of this class is to provide unified interface for user > >> space to get the status and basic information about USB

Re: [PATCH v3 00/13] Virtually mapped stacks with guard pages (x86, core)

On Tuesday, June 21, 2016 10:16:21 AM CEST Kees Cook wrote: > On Tue, Jun 21, 2016 at 2:24 AM, Arnd Bergmann wrote: > > On Monday, June 20, 2016 4:43:30 PM CEST Andy Lutomirski wrote: > >> > >> On my laptop, this adds about 1.5µs of overhead to task creation, > >> which seems to be

Re: [RFC PATCHv2] usb: USB Type-C Connector Class

On Tue, 2016-06-21 at 06:24 -0700, Guenter Roeck wrote: > On 06/21/2016 06:08 AM, Oliver Neukum wrote: > > On Thu, 2016-05-19 at 15:44 +0300, Heikki Krogerus wrote: > >> The purpose of this class is to provide unified interface for user > >> space to get the status and basic information about USB

Re: [PATCH v3 00/13] Virtually mapped stacks with guard pages (x86, core)

On Tuesday, June 21, 2016 10:16:21 AM CEST Kees Cook wrote: > On Tue, Jun 21, 2016 at 2:24 AM, Arnd Bergmann wrote: > > On Monday, June 20, 2016 4:43:30 PM CEST Andy Lutomirski wrote: > >> > >> On my laptop, this adds about 1.5µs of overhead to task creation, > >> which seems to be mainly caused

Re: [PATCH 1/2] workqueue: Move wq_update_unbound_numa() to the beginning of CPU_ONLINE

On Tue, Jun 21, 2016 at 03:43:56PM -0400, Tejun Heo wrote: > On Tue, Jun 21, 2016 at 09:37:09PM +0200, Peter Zijlstra wrote: > > Hurm.. So I've applied it, just to get this issue sorted, but I'm not > > entirely sure I like it. > > > > I think I prefer ego's version because that makes it harder

Re: [PATCH 1/2] workqueue: Move wq_update_unbound_numa() to the beginning of CPU_ONLINE

On Tue, Jun 21, 2016 at 03:43:56PM -0400, Tejun Heo wrote: > On Tue, Jun 21, 2016 at 09:37:09PM +0200, Peter Zijlstra wrote: > > Hurm.. So I've applied it, just to get this issue sorted, but I'm not > > entirely sure I like it. > > > > I think I prefer ego's version because that makes it harder

Re: [kernel-hardening] Re: [PATCH v3 06/13] fork: Add generic vmalloced stack support

On Tue, Jun 21, 2016 at 12:44 PM, Arnd Bergmann wrote: > On Tuesday, June 21, 2016 2:32:28 PM CEST Rik van Riel wrote: >> On Tue, 2016-06-21 at 10:13 -0700, Kees Cook wrote: >> > On Tue, Jun 21, 2016 at 9:59 AM, Andy Lutomirski > > > wrote: >> > > >> > > I'm

Re: [PATCH 1/2] workqueue: Move wq_update_unbound_numa() to the beginning of CPU_ONLINE

On Tue, Jun 21, 2016 at 09:37:09PM +0200, Peter Zijlstra wrote: > Hurm.. So I've applied it, just to get this issue sorted, but I'm not > entirely sure I like it. > > I think I prefer ego's version because that makes it harder to get stuff > to run on !active,online cpus. I think we really want

Re: [kernel-hardening] Re: [PATCH v3 06/13] fork: Add generic vmalloced stack support

On Tue, Jun 21, 2016 at 12:44 PM, Arnd Bergmann wrote: > On Tuesday, June 21, 2016 2:32:28 PM CEST Rik van Riel wrote: >> On Tue, 2016-06-21 at 10:13 -0700, Kees Cook wrote: >> > On Tue, Jun 21, 2016 at 9:59 AM, Andy Lutomirski > > > wrote: >> > > >> > > I'm tempted to explicitly disallow

Re: [PATCH 1/2] workqueue: Move wq_update_unbound_numa() to the beginning of CPU_ONLINE

On Tue, Jun 21, 2016 at 09:37:09PM +0200, Peter Zijlstra wrote: > Hurm.. So I've applied it, just to get this issue sorted, but I'm not > entirely sure I like it. > > I think I prefer ego's version because that makes it harder to get stuff > to run on !active,online cpus. I think we really want

[PATCH] hid-logitech : Dummy hid-lg functions should return proper error code

inline lgff_init stub simply allows compilation on systems with CONFIG_LOGITECH_FF disabled. The inline lgff_init should return -ENODEV instead -1 to indicate lack of support when attempting to register an lg_driver on such a system with CONFIG_LOGITECH_FF disabled. Same for inline lg2ff_init and

[PATCH] hid-logitech : Dummy hid-lg functions should return proper error code

inline lgff_init stub simply allows compilation on systems with CONFIG_LOGITECH_FF disabled. The inline lgff_init should return -ENODEV instead -1 to indicate lack of support when attempting to register an lg_driver on such a system with CONFIG_LOGITECH_FF disabled. Same for inline lg2ff_init and

Re: [Y2038] [PATCH] crypto: Jitter RNG - use ktime_get_raw_ns as fallback

On Tue, Jun 21, 2016 at 12:37 PM, Arnd Bergmann wrote: > On Tuesday, June 21, 2016 12:05:06 PM CEST John Stultz wrote: >> On Tue, Jun 21, 2016 at 11:49 AM, Stephan Mueller >> wrote: >> > Am Dienstag, 21. Juni 2016, 11:11:42 schrieb John Stultz: >> > >> > Hi

Re: [PATCH v4 1/2] Documentation: dt: reset: Add TI syscon reset binding

On Mon, Jun 20, 2016 at 01:46:06PM -0500, Andrew F. Davis wrote: > Add TI syscon reset controller binding. This will hook to the reset > framework and use syscon/regmap to set reset bits. This allows reset > control of individual SoC subsytems and devices with memory-mapped > reset registers in a

Re: [Y2038] [PATCH] crypto: Jitter RNG - use ktime_get_raw_ns as fallback

On Tue, Jun 21, 2016 at 12:37 PM, Arnd Bergmann wrote: > On Tuesday, June 21, 2016 12:05:06 PM CEST John Stultz wrote: >> On Tue, Jun 21, 2016 at 11:49 AM, Stephan Mueller >> wrote: >> > Am Dienstag, 21. Juni 2016, 11:11:42 schrieb John Stultz: >> > >> > Hi John, >> > >> >> I don't see in the

Re: [PATCH v4 1/2] Documentation: dt: reset: Add TI syscon reset binding

On Mon, Jun 20, 2016 at 01:46:06PM -0500, Andrew F. Davis wrote: > Add TI syscon reset controller binding. This will hook to the reset > framework and use syscon/regmap to set reset bits. This allows reset > control of individual SoC subsytems and devices with memory-mapped > reset registers in a

Re: [Y2038] [PATCH] crypto: Jitter RNG - use ktime_get_raw_ns as fallback

On Tuesday, June 21, 2016 12:05:06 PM CEST John Stultz wrote: > On Tue, Jun 21, 2016 at 11:49 AM, Stephan Mueller wrote: > > Am Dienstag, 21. Juni 2016, 11:11:42 schrieb John Stultz: > > > > Hi John, > > > >> I don't see in the above an explanation of *why* you're using > >>

[PATCH] HID-PICOLCD: Dummy hid-picolcd functions should return error code

- inline picolcd_fb_reset and picolcd_init_framebuffer stub simply allows compilation on systems with CONFIG_HID_PICOLCD_FB disabled. - inline picolcd_init_backlight and picolcd_resume_backlight stub simply allows compilation on systems with CONFIG_HID_PICOLCD_BACKLIGHT disabled. - inline

Re: [Y2038] [PATCH] crypto: Jitter RNG - use ktime_get_raw_ns as fallback

On Tuesday, June 21, 2016 12:05:06 PM CEST John Stultz wrote: > On Tue, Jun 21, 2016 at 11:49 AM, Stephan Mueller wrote: > > Am Dienstag, 21. Juni 2016, 11:11:42 schrieb John Stultz: > > > > Hi John, > > > >> I don't see in the above an explanation of *why* you're using > >> ktime_get_raw_ns()

[PATCH] HID-PICOLCD: Dummy hid-picolcd functions should return error code

- inline picolcd_fb_reset and picolcd_init_framebuffer stub simply allows compilation on systems with CONFIG_HID_PICOLCD_FB disabled. - inline picolcd_init_backlight and picolcd_resume_backlight stub simply allows compilation on systems with CONFIG_HID_PICOLCD_BACKLIGHT disabled. - inline

[RESEND PATCH] usb: dwc2: Add reset control to dwc2

From: Dinh Nguyen Allow for platforms that have a reset controller driver in place to bring the USB IP out of reset. Signed-off-by: Dinh Nguyen Acked-by: John Youn Tested-by: Stefan Wahren

[RESEND PATCH] usb: dwc2: Add reset control to dwc2

From: Dinh Nguyen Allow for platforms that have a reset controller driver in place to bring the USB IP out of reset. Signed-off-by: Dinh Nguyen Acked-by: John Youn Tested-by: Stefan Wahren Acked-by: Felipe Balbi --- v7: Use devm_reset_control_get_optional() v6: fix 80 line checkpatch

Re: [PATCH 1/9] regulator: tps65217: Enable suspend configuration

On Mon, Jun 20, 2016 at 02:13:30PM +0530, Keerthy wrote: > +static struct tps65217_regulator_data regulator_data[TPS65217_NUM_REGULATOR]; Why is this a static global? > + /* Store default strobe info */ > + ret = tps65217_reg_read(tps, regulators[i].bypass_reg, ); > + >

Re: [PATCH 1/9] regulator: tps65217: Enable suspend configuration

On Mon, Jun 20, 2016 at 02:13:30PM +0530, Keerthy wrote: > +static struct tps65217_regulator_data regulator_data[TPS65217_NUM_REGULATOR]; Why is this a static global? > + /* Store default strobe info */ > + ret = tps65217_reg_read(tps, regulators[i].bypass_reg, ); > + >

Re: [PATCH] spi: imx: wait_for_completion_timeout(..) for PIO transfers

On Tue, Jun 21, 2016 at 02:12:54PM +0200, Christian Gmeiner wrote: > [ 240.246067] INFO: task hexdump:1660 blocked for more than 120 seconds. > [ 240.246089] Not tainted 4.1.17 001 > [ 240.246099] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables > this message. Please think hard

Re: [PATCH] spi: imx: wait_for_completion_timeout(..) for PIO transfers

On Tue, Jun 21, 2016 at 02:12:54PM +0200, Christian Gmeiner wrote: > [ 240.246067] INFO: task hexdump:1660 blocked for more than 120 seconds. > [ 240.246089] Not tainted 4.1.17 001 > [ 240.246099] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables > this message. Please think hard

Re: [PATCH v4 0/5] /dev/random - a new approach

On 2016-06-21 14:04, Stephan Mueller wrote: Am Dienstag, 21. Juni 2016, 13:51:15 schrieb Austin S. Hemmelgarn: 6. You have a significant lack of data regarding embedded systems, which is one of the two biggest segments of Linux's market share. You list no results for any pre-ARMv6 systems

Re: [PATCH v4 0/5] /dev/random - a new approach

On 2016-06-21 14:04, Stephan Mueller wrote: Am Dienstag, 21. Juni 2016, 13:51:15 schrieb Austin S. Hemmelgarn: 6. You have a significant lack of data regarding embedded systems, which is one of the two biggest segments of Linux's market share. You list no results for any pre-ARMv6 systems

[PATCH v3 8/8] scripts/coccinelle: require coccinelle >= 1.0.4 on device_node_continue.cocci

Make use of the new Requires: tag to be able to specify coccinelle binary version requirements. The cocci file device_node_continue.cocci requires at least coccinelle 1.0.4. Signed-off-by: Luis R. Rodriguez --- scripts/coccinelle/iterators/device_node_continue.cocci | 3 +++

[PATCH v3 8/8] scripts/coccinelle: require coccinelle >= 1.0.4 on device_node_continue.cocci

Make use of the new Requires: tag to be able to specify coccinelle binary version requirements. The cocci file device_node_continue.cocci requires at least coccinelle 1.0.4. Signed-off-by: Luis R. Rodriguez --- scripts/coccinelle/iterators/device_node_continue.cocci | 3 +++ 1 file changed, 3

[PATCH v3 7/8] coccicheck: refer to coccicheck bottest wiki for documentation

Sprinkling *tons* of documentation on the script is not a good idea, instead refer to a wiki for further coccicheck documentation: https://bottest.wiki.kernel.org/coccicheck This page shall always refer to the linux-next iteration of scripts/coccicheck. Signed-off-by: Luis R. Rodriguez

[PATCH v3 6/8] coccicheck: add support for requring a coccinelle version

Enable Coccinelle SmPL patches to require a specific version of Coccinelle. In the event that the version does not match we just inform the user, if the user asked to go through all SmPL patches we just inform them of the need for a new version of coccinelle for the SmPL patch and continue on with

[PATCH v3 5/8] scripts: add Linux .cocciconfig for coccinelle

Help Coccinelle when used against Linux with a set of sensible defaults options for Linux. This hints to coccinelle git can be used for 'git grep' queries over coccigrep. A timeout of 200 seconds should suffice for now. If you use idutils you can override for 'make coccicheck' by using the

[PATCH v3 7/8] coccicheck: refer to coccicheck bottest wiki for documentation

Sprinkling *tons* of documentation on the script is not a good idea, instead refer to a wiki for further coccicheck documentation: https://bottest.wiki.kernel.org/coccicheck This page shall always refer to the linux-next iteration of scripts/coccicheck. Signed-off-by: Luis R. Rodriguez ---

<    2   3   4   5   6   7   8   9   10   11   >