Linux 3.18.105

I'm announcing the release of the 3.18.105 kernel. All users of the 3.18 kernel series must upgrade. The updated 3.18.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.18.y and can be browsed at the normal kernel.org git web

Linux 3.18.105

I'm announcing the release of the 3.18.105 kernel. All users of the 3.18 kernel series must upgrade. The updated 3.18.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.18.y and can be browsed at the normal kernel.org git web

Re: Linux 3.18.105

diff --git a/Makefile b/Makefile index 2eae8b1039aa..ba34e4e77d96 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 3 PATCHLEVEL = 18 -SUBLEVEL = 104 +SUBLEVEL = 105 EXTRAVERSION = NAME = Diseased Newt diff --git a/arch/arm/boot/dts/imx6qdl-wandboard.dtsi

Re: Linux 3.18.105

diff --git a/Makefile b/Makefile index 2eae8b1039aa..ba34e4e77d96 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 3 PATCHLEVEL = 18 -SUBLEVEL = 104 +SUBLEVEL = 105 EXTRAVERSION = NAME = Diseased Newt diff --git a/arch/arm/boot/dts/imx6qdl-wandboard.dtsi

Linux 4.4.128

I'm announcing the release of the 4.4.128 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Linux 4.4.128

I'm announcing the release of the 4.4.128 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Linux 4.9.94

I'm announcing the release of the 4.9.94 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Linux 4.9.94

I'm announcing the release of the 4.9.94 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Re: [PATCH 07/24] hibernate: Disable when the kernel is locked down

On Wed 2018-04-11 17:25:25, David Howells wrote: > From: Josh Boyer > > There is currently no way to verify the resume image when returning > from hibernate. This might compromise the signed modules trust model, > so until we can work with signed hibernate images we

Re: [PATCH 24/24] debugfs: Restrict debugfs when the kernel is locked down

On Wed 2018-04-11 17:27:16, David Howells wrote: > Disallow opening of debugfs files that might be used to muck around when > the kernel is locked down as various drivers give raw access to hardware > through debugfs. Given the effort of auditing all 2000 or so files and > manually fixing each

Re: [PATCH 07/24] hibernate: Disable when the kernel is locked down

On Wed 2018-04-11 17:25:25, David Howells wrote: > From: Josh Boyer > > There is currently no way to verify the resume image when returning > from hibernate. This might compromise the signed modules trust model, > so until we can work with signed hibernate images we disable it when the > kernel

Re: [PATCH 24/24] debugfs: Restrict debugfs when the kernel is locked down

On Wed 2018-04-11 17:27:16, David Howells wrote: > Disallow opening of debugfs files that might be used to muck around when > the kernel is locked down as various drivers give raw access to hardware > through debugfs. Given the effort of auditing all 2000 or so files and > manually fixing each

Re: [PATCH 02/24] Add a SysRq option to lift kernel lockdown

On Wed 2018-04-11 17:24:52, David Howells wrote: > From: Kyle McMartin > > Make an option to provide a sysrq key that will lift the kernel lockdown, > thereby allowing the running kernel image to be accessed and modified. > > On x86 this is triggered with SysRq+x, but this key

Re: [PATCH 02/24] Add a SysRq option to lift kernel lockdown

On Wed 2018-04-11 17:24:52, David Howells wrote: > From: Kyle McMartin > > Make an option to provide a sysrq key that will lift the kernel lockdown, > thereby allowing the running kernel image to be accessed and modified. > > On x86 this is triggered with SysRq+x, but this key may not be

Re: [PATCH 00/32] docs/vm: convert to ReST format

On Fri, Apr 13, 2018 at 01:55:51PM -0600, Jonathan Corbet wrote: > > I believe that keeping the mm docs together will give better visibility of > > what (little) mm documentation we have and will make the updates easier. > > The documents that fit well into a certain topic could be linked there.

Re: [PATCH 00/32] docs/vm: convert to ReST format

On Fri, Apr 13, 2018 at 01:55:51PM -0600, Jonathan Corbet wrote: > > I believe that keeping the mm docs together will give better visibility of > > what (little) mm documentation we have and will make the updates easier. > > The documents that fit well into a certain topic could be linked there.

Re: [PATCH 1/6] fs: use << for MS_* flags

On Fri, Apr 13, 2018 at 09:45:01AM -0700, Randy Dunlap wrote: > On 04/13/2018 09:11 AM, Christian Brauner wrote: > > Consistenly use << to define MS_* constants. > > > > Signed-off-by: Christian Brauner > > --- > > include/uapi/linux/fs.h | 33

Re: [PATCH 1/6] fs: use << for MS_* flags

On Fri, Apr 13, 2018 at 09:45:01AM -0700, Randy Dunlap wrote: > On 04/13/2018 09:11 AM, Christian Brauner wrote: > > Consistenly use << to define MS_* constants. > > > > Signed-off-by: Christian Brauner > > --- > > include/uapi/linux/fs.h | 33 + > > 1 file

Re: [PATCH] parisc: Switch to generic COMPAT_BINFMT_ELF

On Fri, Apr 13, 2018 at 09:54:37PM +0200, Helge Deller wrote: > * Guenter Roeck : > > On Wed, Apr 11, 2018 at 09:09:53AM +0200, Helge Deller wrote: > > > Drop our own compat binfmt implementation in > > > arch/parisc/kernel/binfmt_elf32.c in favour of the generic > > >

Re: [PATCH] sched: support dynamiQ cluster

On Fri, Apr 6, 2018 at 5:58 AM, Morten Rasmussen wrote: > On Thu, Apr 05, 2018 at 06:22:48PM +0200, Vincent Guittot wrote: >> Hi Morten, >> >> On 5 April 2018 at 17:46, Morten Rasmussen wrote: >> > On Wed, Apr 04, 2018 at 03:43:17PM +0200,

Re: [PATCH] parisc: Switch to generic COMPAT_BINFMT_ELF

On Fri, Apr 13, 2018 at 09:54:37PM +0200, Helge Deller wrote: > * Guenter Roeck : > > On Wed, Apr 11, 2018 at 09:09:53AM +0200, Helge Deller wrote: > > > Drop our own compat binfmt implementation in > > > arch/parisc/kernel/binfmt_elf32.c in favour of the generic > > > implementation with

Re: [PATCH] sched: support dynamiQ cluster

On Fri, Apr 6, 2018 at 5:58 AM, Morten Rasmussen wrote: > On Thu, Apr 05, 2018 at 06:22:48PM +0200, Vincent Guittot wrote: >> Hi Morten, >> >> On 5 April 2018 at 17:46, Morten Rasmussen wrote: >> > On Wed, Apr 04, 2018 at 03:43:17PM +0200, Vincent Guittot wrote: >> >> On 4 April 2018 at 12:44,

Re: [PATCH 00/32] docs/vm: convert to ReST format

Sorry for the silence, I'm pedaling as fast as I can, honest... On Sun, 1 Apr 2018 09:38:58 +0300 Mike Rapoport wrote: > My thinking was to start with mechanical RST conversion and then to start > working on the contents and ordering of the documentation. Some of the >

Re: [PATCH 00/32] docs/vm: convert to ReST format

Sorry for the silence, I'm pedaling as fast as I can, honest... On Sun, 1 Apr 2018 09:38:58 +0300 Mike Rapoport wrote: > My thinking was to start with mechanical RST conversion and then to start > working on the contents and ordering of the documentation. Some of the > existing files, e.g.

Re: [PATCH] parisc: Switch to generic COMPAT_BINFMT_ELF

* Guenter Roeck : > On Wed, Apr 11, 2018 at 09:09:53AM +0200, Helge Deller wrote: > > Drop our own compat binfmt implementation in > > arch/parisc/kernel/binfmt_elf32.c in favour of the generic > > implementation with CONFIG_COMPAT_BINFMT_ELF. > > > > While cleaning up the

Re: [PATCH] parisc: Switch to generic COMPAT_BINFMT_ELF

* Guenter Roeck : > On Wed, Apr 11, 2018 at 09:09:53AM +0200, Helge Deller wrote: > > Drop our own compat binfmt implementation in > > arch/parisc/kernel/binfmt_elf32.c in favour of the generic > > implementation with CONFIG_COMPAT_BINFMT_ELF. > > > > While cleaning up the dependencies, I noticed

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Fri, Apr 13, 2018 at 11:45 AM, Dave Martin wrote: > > Most uses I've seen do nothing more than use the FPE_xyz value to > format diagnostic messages while dying. I struggled to find code that > made a meaningful functional decision based on the value, though that's > not

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Fri, Apr 13, 2018 at 11:45 AM, Dave Martin wrote: > > Most uses I've seen do nothing more than use the FPE_xyz value to > format diagnostic messages while dying. I struggled to find code that > made a meaningful functional decision based on the value, though that's > not proof... Yeah. I've

RE: [PATCH v1 4/7] platform: mellanox: add new ODM system types to mlx-platform

> -Original Message- > From: Darren Hart [mailto:dvh...@infradead.org] > Sent: Friday, April 13, 2018 7:55 PM > To: Vadim Pasternak > Cc: andy.shevche...@gmail.com; gre...@linuxfoundation.org; linux- > ker...@vger.kernel.org; platform-driver-...@vger.kernel.org;

RE: [PATCH v1 4/7] platform: mellanox: add new ODM system types to mlx-platform

> -Original Message- > From: Darren Hart [mailto:dvh...@infradead.org] > Sent: Friday, April 13, 2018 7:55 PM > To: Vadim Pasternak > Cc: andy.shevche...@gmail.com; gre...@linuxfoundation.org; linux- > ker...@vger.kernel.org; platform-driver-...@vger.kernel.org; j...@resnulli.us; >

RE: [PATCH v1 3/7] platform/mellanox: mlxreg-hotplug: add extra cycle for hotplug work queue

> -Original Message- > From: Darren Hart [mailto:dvh...@infradead.org] > Sent: Friday, April 13, 2018 7:47 PM > To: Vadim Pasternak > Cc: andy.shevche...@gmail.com; gre...@linuxfoundation.org; linux- > ker...@vger.kernel.org; platform-driver-...@vger.kernel.org;

RE: [PATCH v1 3/7] platform/mellanox: mlxreg-hotplug: add extra cycle for hotplug work queue

> -Original Message- > From: Darren Hart [mailto:dvh...@infradead.org] > Sent: Friday, April 13, 2018 7:47 PM > To: Vadim Pasternak > Cc: andy.shevche...@gmail.com; gre...@linuxfoundation.org; linux- > ker...@vger.kernel.org; platform-driver-...@vger.kernel.org; j...@resnulli.us; >

[PULL REQUEST] i2c for 4.17

Linus, the second pull request from I2C contains: - hot bugfix for i801 to make laptops with strange BIOS reboot again when using SMBUS Host notify - change to MAINTAINERS creating a specific fallback entry for I2C host drivers and settings its status to "Odd fixes" - a long overdue param

[PULL REQUEST] i2c for 4.17

Linus, the second pull request from I2C contains: - hot bugfix for i801 to make laptops with strange BIOS reboot again when using SMBUS Host notify - change to MAINTAINERS creating a specific fallback entry for I2C host drivers and settings its status to "Odd fixes" - a long overdue param

Re: [PATCH] kasan: add no_sanitize attribute for clang builds

On 04/13/2018 08:34 PM, Andrey Konovalov wrote: > On Fri, Apr 13, 2018 at 5:31 PM, Andrey Ryabinin > wrote: >> >> >> On 04/12/2018 08:29 PM, Andrey Konovalov wrote: >>> KASAN uses the __no_sanitize_address macro to disable instrumentation >>> of particular functions.

Re: [PATCH] kasan: add no_sanitize attribute for clang builds

On 04/13/2018 08:34 PM, Andrey Konovalov wrote: > On Fri, Apr 13, 2018 at 5:31 PM, Andrey Ryabinin > wrote: >> >> >> On 04/12/2018 08:29 PM, Andrey Konovalov wrote: >>> KASAN uses the __no_sanitize_address macro to disable instrumentation >>> of particular functions. Right now it's defined only

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Fri, Apr 13, 2018 at 07:50:17PM +0100, Russell King - ARM Linux wrote: > On Fri, Apr 13, 2018 at 07:35:38PM +0100, Dave Martin wrote: > > If that's the case though, I don't see how a userspace testsuite is > > hitting this code path. Maybe I've misunderstood the context of this > > thread. >

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Fri, Apr 13, 2018 at 07:50:17PM +0100, Russell King - ARM Linux wrote: > On Fri, Apr 13, 2018 at 07:35:38PM +0100, Dave Martin wrote: > > If that's the case though, I don't see how a userspace testsuite is > > hitting this code path. Maybe I've misunderstood the context of this > > thread. >

[PATCH] trace_kprobe: Remove warning message "Could not insert probe at..."

This warning message is not very helpful, as the return value should already show information about the error. Also, this message will flush dmesg if the user space do something silly in a loop, like: for x in {0..5} do echo p:xx xx+$x >> /sys/kernel/debug/tracing/kprobe_events

[PATCH] trace_kprobe: Remove warning message "Could not insert probe at..."

This warning message is not very helpful, as the return value should already show information about the error. Also, this message will flush dmesg if the user space do something silly in a loop, like: for x in {0..5} do echo p:xx xx+$x >> /sys/kernel/debug/tracing/kprobe_events

Re: [PATCH] virtio_balloon: add array of stat names

On 04/13/2018 06:44 AM, Michael S. Tsirkin wrote: Jason Wang points out that it's vary hard for users to build an array of s/vary/very stat names. The naive thing is to use VIRTIO_BALLOON_S_NR but that breaks if we add more stats. Let's add an array of reasonably readable names. Thanks

Re: [PATCH] virtio_balloon: add array of stat names

On 04/13/2018 06:44 AM, Michael S. Tsirkin wrote: Jason Wang points out that it's vary hard for users to build an array of s/vary/very stat names. The naive thing is to use VIRTIO_BALLOON_S_NR but that breaks if we add more stats. Let's add an array of reasonably readable names. Thanks

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Fri, Apr 13, 2018 at 07:35:38PM +0100, Dave Martin wrote: > If that's the case though, I don't see how a userspace testsuite is > hitting this code path. Maybe I've misunderstood the context of this > thread. It isn't hitting this exact case. The userspace testsuite is hitting an entirely

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Fri, Apr 13, 2018 at 07:35:38PM +0100, Dave Martin wrote: > If that's the case though, I don't see how a userspace testsuite is > hitting this code path. Maybe I've misunderstood the context of this > thread. It isn't hitting this exact case. The userspace testsuite is hitting an entirely

Re: [PATCH] Documentation/i2c: sync docs with current state of i2c-tools.

On Fri, 13 Apr 2018 09:02:03 -0700, Sam Hansen wrote: > On Fri, Apr 13, 2018 at 5:13 AM, Jean Delvare wrote: > > On Fri, 13 Apr 2018 00:24:57 +0200, Wolfram Sang wrote: > >> On Thu, Apr 12, 2018 at 02:33:42PM -0700, Sam Hansen wrote: > >> > - Not meant to be called

Re: [PATCH] Documentation/i2c: sync docs with current state of i2c-tools.

On Fri, 13 Apr 2018 09:02:03 -0700, Sam Hansen wrote: > On Fri, Apr 13, 2018 at 5:13 AM, Jean Delvare wrote: > > On Fri, 13 Apr 2018 00:24:57 +0200, Wolfram Sang wrote: > >> On Thu, Apr 12, 2018 at 02:33:42PM -0700, Sam Hansen wrote: > >> > - Not meant to be called directly; instead, use

Re: [PATCH 1/3] USB: musb: dsps: drop duplicate phy initialisation

On Fri, Apr 13, 2018 at 05:15:03PM +0200, Johan Hovold wrote: > Since commit 39cee200c23e ("usb: musb: core: call init and shutdown for > the usb phy") the musb USB phy is initialised by musb_core, but the > original initialisation in the dsps-glue init callback was left in > place resulting in

Re: [PATCH 1/3] USB: musb: dsps: drop duplicate phy initialisation

On Fri, Apr 13, 2018 at 05:15:03PM +0200, Johan Hovold wrote: > Since commit 39cee200c23e ("usb: musb: core: call init and shutdown for > the usb phy") the musb USB phy is initialised by musb_core, but the > original initialisation in the dsps-glue init callback was left in > place resulting in

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Fri, Apr 13, 2018 at 11:23:36AM -0700, Linus Torvalds wrote: > On Fri, Apr 13, 2018 at 10:54 AM, Russell King - ARM Linux > wrote: > > > > FPE_FLTINV means "floating point invalid operation". Does it really > > cover the case where hardware has failed, or is it intended

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Fri, Apr 13, 2018 at 11:23:36AM -0700, Linus Torvalds wrote: > On Fri, Apr 13, 2018 at 10:54 AM, Russell King - ARM Linux > wrote: > > > > FPE_FLTINV means "floating point invalid operation". Does it really > > cover the case where hardware has failed, or is it intended to cover > > the case

[PATCH v2] powerpc/sparse: fix plain integer as NULL pointer warning

Trivial fix to remove the following sparse warnings: arch/powerpc/kernel/module_32.c:112:74: warning: Using plain integer as NULL pointer arch/powerpc/kernel/module_32.c:117:74: warning: Using plain integer as NULL pointer drivers/macintosh/via-pmu.c:1155:28: warning: Using plain integer

[PATCH v2] powerpc/sparse: fix plain integer as NULL pointer warning

Trivial fix to remove the following sparse warnings: arch/powerpc/kernel/module_32.c:112:74: warning: Using plain integer as NULL pointer arch/powerpc/kernel/module_32.c:117:74: warning: Using plain integer as NULL pointer drivers/macintosh/via-pmu.c:1155:28: warning: Using plain integer

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Fri, Apr 13, 2018 at 06:54:08PM +0100, Russell King - ARM Linux wrote: > On Fri, Apr 13, 2018 at 06:08:28PM +0100, Dave Martin wrote: > > On Fri, Apr 13, 2018 at 09:33:17AM -0700, Linus Torvalds wrote: > > > On Fri, Apr 13, 2018 at 2:42 AM, Russell King - ARM Linux > > >

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Fri, Apr 13, 2018 at 06:54:08PM +0100, Russell King - ARM Linux wrote: > On Fri, Apr 13, 2018 at 06:08:28PM +0100, Dave Martin wrote: > > On Fri, Apr 13, 2018 at 09:33:17AM -0700, Linus Torvalds wrote: > > > On Fri, Apr 13, 2018 at 2:42 AM, Russell King - ARM Linux > > > wrote: > > > > > > > >

Re: [PATCH v3 05/11] dt-bindings: input: touchscreen: resistive-adc-touch: create bindings

On Tue, Apr 10, 2018 at 11:57:51AM +0300, Eugen Hristev wrote: > Added bindings for generic resistive touchscreen ADC. > > Signed-off-by: Eugen Hristev > --- > Changes in v3: > - renamed file and compatible to exclude "generic" keyword > - removed the pressure

Re: [PATCH v3 05/11] dt-bindings: input: touchscreen: resistive-adc-touch: create bindings

On Tue, Apr 10, 2018 at 11:57:51AM +0300, Eugen Hristev wrote: > Added bindings for generic resistive touchscreen ADC. > > Signed-off-by: Eugen Hristev > --- > Changes in v3: > - renamed file and compatible to exclude "generic" keyword > - removed the pressure threshold property, added it as a

Re: [PATCH 2/6] statfs: use << to align with fs header

On Fri, Apr 13, 2018 at 10:55:23AM -0700, Randy Dunlap wrote: > On 04/13/2018 10:35 AM, Andreas Dilger wrote: > > On Apr 13, 2018, at 10:11 AM, Christian Brauner > > wrote: > >> > >> Consistenly use << to define ST_* constants. This also aligns them with > >> their

Re: [PATCH 2/6] statfs: use << to align with fs header

On Fri, Apr 13, 2018 at 10:55:23AM -0700, Randy Dunlap wrote: > On 04/13/2018 10:35 AM, Andreas Dilger wrote: > > On Apr 13, 2018, at 10:11 AM, Christian Brauner > > wrote: > >> > >> Consistenly use << to define ST_* constants. This also aligns them with > >> their MS_* counterparts in fs.h > >

Re: [PATCH v3 04/11] dt-bindings: input: touchscreen: add pressure threshold touchscreen property

On Tue, Apr 10, 2018 at 11:57:50AM +0300, Eugen Hristev wrote: > Add a common touchscreen optional property that will specify > the minimum pressure applied to the screen that is needed > such that the driver will report the touch event. > > Signed-off-by: Eugen Hristev

Re: [PATCH v3 04/11] dt-bindings: input: touchscreen: add pressure threshold touchscreen property

On Tue, Apr 10, 2018 at 11:57:50AM +0300, Eugen Hristev wrote: > Add a common touchscreen optional property that will specify > the minimum pressure applied to the screen that is needed > such that the driver will report the touch event. > > Signed-off-by: Eugen Hristev > --- >

Re: [PATCH v4 5/8] dt-bindings: arm: Document the RZN1D-DB board

On Tue, Apr 10, 2018 at 09:30:05AM +0100, Michel Pollet wrote: > This documents the RZ/N1 bindings for the RZN1D-DB board. > > Signed-off-by: Michel Pollet > --- > Documentation/devicetree/bindings/arm/shmobile.txt | 5 - > 1 file changed, 4 insertions(+), 1

Re: [PATCH v4 5/8] dt-bindings: arm: Document the RZN1D-DB board

On Tue, Apr 10, 2018 at 09:30:05AM +0100, Michel Pollet wrote: > This documents the RZ/N1 bindings for the RZN1D-DB board. > > Signed-off-by: Michel Pollet > --- > Documentation/devicetree/bindings/arm/shmobile.txt | 5 - > 1 file changed, 4 insertions(+), 1 deletion(-) Reviewed-by: Rob

Re: [PATCH] parisc: Switch to generic COMPAT_BINFMT_ELF

On Wed, Apr 11, 2018 at 09:09:53AM +0200, Helge Deller wrote: > Drop our own compat binfmt implementation in > arch/parisc/kernel/binfmt_elf32.c in favour of the generic > implementation with CONFIG_COMPAT_BINFMT_ELF. > > While cleaning up the dependencies, I noticed that ELF_PLATFORM was

Re: [PATCH] parisc: Switch to generic COMPAT_BINFMT_ELF

On Wed, Apr 11, 2018 at 09:09:53AM +0200, Helge Deller wrote: > Drop our own compat binfmt implementation in > arch/parisc/kernel/binfmt_elf32.c in favour of the generic > implementation with CONFIG_COMPAT_BINFMT_ELF. > > While cleaning up the dependencies, I noticed that ELF_PLATFORM was

Re: WARNING in up_write

On Fri, Apr 6, 2018 at 4:01 AM, Dave Chinner wrote: > On Thu, Apr 05, 2018 at 05:13:25PM -0700, Eric Biggers wrote: >> On Fri, Apr 06, 2018 at 08:32:26AM +1000, Dave Chinner wrote: >> > On Wed, Apr 04, 2018 at 08:24:54PM -0700, Matthew Wilcox wrote: >> > > On Wed, Apr 04,

Re: WARNING in up_write

On Fri, Apr 6, 2018 at 4:01 AM, Dave Chinner wrote: > On Thu, Apr 05, 2018 at 05:13:25PM -0700, Eric Biggers wrote: >> On Fri, Apr 06, 2018 at 08:32:26AM +1000, Dave Chinner wrote: >> > On Wed, Apr 04, 2018 at 08:24:54PM -0700, Matthew Wilcox wrote: >> > > On Wed, Apr 04, 2018 at 11:22:00PM

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Fri, Apr 13, 2018 at 10:54 AM, Russell King - ARM Linux wrote: > > FPE_FLTINV means "floating point invalid operation". Does it really > cover the case where hardware has failed, or is it intended to cover > the case where userspace did something wrong and asked for an

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Fri, Apr 13, 2018 at 10:54 AM, Russell King - ARM Linux wrote: > > FPE_FLTINV means "floating point invalid operation". Does it really > cover the case where hardware has failed, or is it intended to cover > the case where userspace did something wrong and asked for an invalid > operation

Re: [PATCH v2 2/3] usb: dwc3: Add Qualcomm DWC3 glue driver

On Fri, Apr 13, 2018 at 11:32:04PM +0530, Manu Gautam wrote: > On 4/13/2018 11:03 PM, Jack Pham wrote: > > Are the extcon phandles bound to the glue node? I don't see the > > description in the bindings doc in PATCH 1/3. And if so, would it be > > a duplicate of the child node's extcon binding?

Re: [PATCH v2 2/3] usb: dwc3: Add Qualcomm DWC3 glue driver

On Fri, Apr 13, 2018 at 11:32:04PM +0530, Manu Gautam wrote: > On 4/13/2018 11:03 PM, Jack Pham wrote: > > Are the extcon phandles bound to the glue node? I don't see the > > description in the bindings doc in PATCH 1/3. And if so, would it be > > a duplicate of the child node's extcon binding?

Re: [PATCH] x86/cpufeature: guard asm_volatile_goto usage with CC_HAVE_ASM_GOTO

On Tue, Apr 10, 2018 at 02:28:04PM -0700, Alexei Starovoitov wrote: > Instead of > #ifdef CC_HAVE_ASM_GOTO > we can replace it with > #ifndef __BPF__ > or some other name, I would prefer the BPF specific hack; otherwise we might be encouraging people to build the kernel proper without asm-goto.

Re: [PATCH] x86/cpufeature: guard asm_volatile_goto usage with CC_HAVE_ASM_GOTO

On Tue, Apr 10, 2018 at 02:28:04PM -0700, Alexei Starovoitov wrote: > Instead of > #ifdef CC_HAVE_ASM_GOTO > we can replace it with > #ifndef __BPF__ > or some other name, I would prefer the BPF specific hack; otherwise we might be encouraging people to build the kernel proper without asm-goto.

[PATCH] PCI: Add PCIe to pcie_print_link_status() messages

Currently the pcie_print_link_status() will print PCIe bandwidth and link width information but does not mention it is pertaining to the PCIe. Since this and related functions are used exclusively by networking drivers today users may get confused into thinking that it's the NIC bandwidth that is

[PATCH] PCI: Add PCIe to pcie_print_link_status() messages

Currently the pcie_print_link_status() will print PCIe bandwidth and link width information but does not mention it is pertaining to the PCIe. Since this and related functions are used exclusively by networking drivers today users may get confused into thinking that it's the NIC bandwidth that is

Re: [PATCH 2/3] dt-bindings: add binding for at91-usart in spi mode

On 13/04/2018 19:12:54+0200, Nicolas Ferre wrote: > > > diff --git > > > a/Documentation/devicetree/bindings/spi/microchip,at91-usart-spi.txt > > > b/Documentation/devicetree/bindings/spi/microchip,at91-usart-spi.txt > > > new file mode 100644 > > > index ..92d33ccdffae > > > ---

Re: [PATCH 2/3] dt-bindings: add binding for at91-usart in spi mode

On 13/04/2018 19:12:54+0200, Nicolas Ferre wrote: > > > diff --git > > > a/Documentation/devicetree/bindings/spi/microchip,at91-usart-spi.txt > > > b/Documentation/devicetree/bindings/spi/microchip,at91-usart-spi.txt > > > new file mode 100644 > > > index ..92d33ccdffae > > > ---

Re: [PATCH 21/30] stack-protector: test compiler capability in Kconfig and drop AUTO mode

On Fri, Apr 13, 2018 at 9:41 AM, Kees Cook wrote: > > How about something like this instead: I'd rather avoid the ifdef's in the Makefile if at all possible. I'd rather expose this as a Kconfig rule, and in the Kconfig just have an entry something like this config

Re: [PATCH 21/30] stack-protector: test compiler capability in Kconfig and drop AUTO mode

On Fri, Apr 13, 2018 at 9:41 AM, Kees Cook wrote: > > How about something like this instead: I'd rather avoid the ifdef's in the Makefile if at all possible. I'd rather expose this as a Kconfig rule, and in the Kconfig just have an entry something like this config STACKPROTECTOR_FLAGS

[Regression] PCI / PM: Simplify device wakeup settings code

Hi Rafael, A kernel bug report was opened against Ubuntu [0].  After a kernel bisect, it was found that reverting the following two commits resolved this bug: 0ce3fcaff929 ("PCI / PM: Restore PME Enable after config space restoration") 0847684cfc5f("PCI / PM: Simplify device wakeup settings

[Regression] PCI / PM: Simplify device wakeup settings code

Hi Rafael, A kernel bug report was opened against Ubuntu [0].  After a kernel bisect, it was found that reverting the following two commits resolved this bug: 0ce3fcaff929 ("PCI / PM: Restore PME Enable after config space restoration") 0847684cfc5f("PCI / PM: Simplify device wakeup settings

Re: [RFC PATCH for 4.18 12/23] cpu_opv: Provide cpu_opv system call (v7)

- On Apr 13, 2018, at 12:37 PM, Linus Torvalds torva...@linux-foundation.org wrote: > On Fri, Apr 13, 2018 at 5:16 AM, Mathieu Desnoyers > wrote: >> The vmalloc space needed by cpu_opv is bound by the number of pages >> a cpu_opv call can touch. > > No it's

Re: [RFC PATCH for 4.18 12/23] cpu_opv: Provide cpu_opv system call (v7)

- On Apr 13, 2018, at 12:37 PM, Linus Torvalds torva...@linux-foundation.org wrote: > On Fri, Apr 13, 2018 at 5:16 AM, Mathieu Desnoyers > wrote: >> The vmalloc space needed by cpu_opv is bound by the number of pages >> a cpu_opv call can touch. > > No it's not. > > You can have a

Re: [PATCH v4 3/8] dt-bindings: mfd: renesas,rzn1-sysctrl: document RZ/N1 sysctrl node

On Tue, Apr 10, 2018 at 09:30:03AM +0100, Michel Pollet wrote: > The Renesas RZ/N1 Family (Part #R9A06G0xx) has a multi-function > system controller. This documents the node used to encapsulate > it's sub drivers. > > Signed-off-by: Michel Pollet > --- >

Re: [PATCH v4 3/8] dt-bindings: mfd: renesas,rzn1-sysctrl: document RZ/N1 sysctrl node

On Tue, Apr 10, 2018 at 09:30:03AM +0100, Michel Pollet wrote: > The Renesas RZ/N1 Family (Part #R9A06G0xx) has a multi-function > system controller. This documents the node used to encapsulate > it's sub drivers. > > Signed-off-by: Michel Pollet > --- >

Re: [PATCH 1/2] dt-bindings/display/bridge: sii902x: add optional power supplies

On Tue, Apr 10, 2018 at 07:19:26AM +0200, Philippe Cornu wrote: > Add the 3 optional power supplies using the exact description > found in the document named > "SiI9022A/SiI9024A HDMI Transmitter Data Sheet (August 2016)". > > Signed-off-by: Philippe Cornu > --- >

Re: [PATCH 1/2] dt-bindings/display/bridge: sii902x: add optional power supplies

On Tue, Apr 10, 2018 at 07:19:26AM +0200, Philippe Cornu wrote: > Add the 3 optional power supplies using the exact description > found in the document named > "SiI9022A/SiI9024A HDMI Transmitter Data Sheet (August 2016)". > > Signed-off-by: Philippe Cornu > --- >

Re: [PATCH] spi: cadence: Add usleep_range() for cdns_spi_fill_tx_fifo()

On Mon, Apr 09, 2018 at 07:16:50PM +0800, sxauwsk wrote: > In case of xspi work in busy condition, may send bytes failed. > Add one bytes delay > while ((trans_cnt < CDNS_SPI_FIFO_DEPTH) && > (xspi->tx_bytes > 0)) { > + > + /* When xspi in busy condition, bytes may

Re: [PATCH] spi: cadence: Add usleep_range() for cdns_spi_fill_tx_fifo()

On Mon, Apr 09, 2018 at 07:16:50PM +0800, sxauwsk wrote: > In case of xspi work in busy condition, may send bytes failed. > Add one bytes delay > while ((trans_cnt < CDNS_SPI_FIFO_DEPTH) && > (xspi->tx_bytes > 0)) { > + > + /* When xspi in busy condition, bytes may

Re: [PATCH v2 2/3] usb: dwc3: Add Qualcomm DWC3 glue driver

Hi Jack, On 4/13/2018 11:03 PM, Jack Pham wrote: > Hi Manu, > > On Fri, Apr 13, 2018 at 10:21:23PM +0530, Manu Gautam wrote: >> DWC3 controller on Qualcomm SOCs has a Qscratch wrapper. >> Some of its uses are described below resulting in need to >> have a separate glue driver instead of using

Re: [PATCH v2 2/3] usb: dwc3: Add Qualcomm DWC3 glue driver

Hi Jack, On 4/13/2018 11:03 PM, Jack Pham wrote: > Hi Manu, > > On Fri, Apr 13, 2018 at 10:21:23PM +0530, Manu Gautam wrote: >> DWC3 controller on Qualcomm SOCs has a Qscratch wrapper. >> Some of its uses are described below resulting in need to >> have a separate glue driver instead of using

Re: Crashes/hung tasks with z3pool under memory pressure

On Fri, Apr 13, 2018 at 05:40:18PM +, Vitaly Wool wrote: > On Fri, Apr 13, 2018, 7:35 PM Guenter Roeck wrote: > > > On Fri, Apr 13, 2018 at 05:21:02AM +, Vitaly Wool wrote: > > > Hi Guenter, > > > > > > > > > Den fre 13 apr. 2018 kl 00:01 skrev Guenter Roeck

Re: Crashes/hung tasks with z3pool under memory pressure

On Fri, Apr 13, 2018 at 05:40:18PM +, Vitaly Wool wrote: > On Fri, Apr 13, 2018, 7:35 PM Guenter Roeck wrote: > > > On Fri, Apr 13, 2018 at 05:21:02AM +, Vitaly Wool wrote: > > > Hi Guenter, > > > > > > > > > Den fre 13 apr. 2018 kl 00:01 skrev Guenter Roeck : > > > > > > > Hi all, > > >

Re: [PATCH 1/3] drm/vc4: Remove the need for the GPU-subsystem DT node.

On Mon, Apr 09, 2018 at 04:00:38PM -0700, Eric Anholt wrote: > The GPU subsystem node was a workaround to have a central device to > bind V3D and display to. Following the lead of 246774d17fc0 > ("drm/etnaviv: remove the need for a gpu-subsystem DT node"), remove > the subsystem node usage and

Re: [PATCH 1/3] drm/vc4: Remove the need for the GPU-subsystem DT node.

On Mon, Apr 09, 2018 at 04:00:38PM -0700, Eric Anholt wrote: > The GPU subsystem node was a workaround to have a central device to > bind V3D and display to. Following the lead of 246774d17fc0 > ("drm/etnaviv: remove the need for a gpu-subsystem DT node"), remove > the subsystem node usage and

Re: [PATCH 2/6] statfs: use << to align with fs header

On 04/13/2018 10:35 AM, Andreas Dilger wrote: > On Apr 13, 2018, at 10:11 AM, Christian Brauner > wrote: >> >> Consistenly use << to define ST_* constants. This also aligns them with >> their MS_* counterparts in fs.h > > IMHO, using (1 << 10) makes the code harder

Re: [PATCH 2/6] statfs: use << to align with fs header

On 04/13/2018 10:35 AM, Andreas Dilger wrote: > On Apr 13, 2018, at 10:11 AM, Christian Brauner > wrote: >> >> Consistenly use << to define ST_* constants. This also aligns them with >> their MS_* counterparts in fs.h > > IMHO, using (1 << 10) makes the code harder to debug. If you see a field

[PATCH] proc: fix /proc/loadavg regression

commit 95846ecf9dac5089aed4b144d912225f8ef86ae4 "pid: replace pid bitmap implementation with IDR API" changed last field of /proc/loadavg (last pid allocated) to be off by one: # unshare -p -f --mount-proc cat /proc/loadavg 0.00 0.00 0.00 1/60 2 <=== It should be 1 after first

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Fri, Apr 13, 2018 at 06:08:28PM +0100, Dave Martin wrote: > On Fri, Apr 13, 2018 at 09:33:17AM -0700, Linus Torvalds wrote: > > On Fri, Apr 13, 2018 at 2:42 AM, Russell King - ARM Linux > > wrote: > > > > > > Yes, it does solve the problem at hand with strace - the exact

[PATCH] proc: fix /proc/loadavg regression

commit 95846ecf9dac5089aed4b144d912225f8ef86ae4 "pid: replace pid bitmap implementation with IDR API" changed last field of /proc/loadavg (last pid allocated) to be off by one: # unshare -p -f --mount-proc cat /proc/loadavg 0.00 0.00 0.00 1/60 2 <=== It should be 1 after first

Re: sparc/ppc/arm compat siginfo ABI regressions: sending SIGFPE via kill() returns wrong values in si_pid and si_uid

On Fri, Apr 13, 2018 at 06:08:28PM +0100, Dave Martin wrote: > On Fri, Apr 13, 2018 at 09:33:17AM -0700, Linus Torvalds wrote: > > On Fri, Apr 13, 2018 at 2:42 AM, Russell King - ARM Linux > > wrote: > > > > > > Yes, it does solve the problem at hand with strace - the exact patch I > > > tested

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