Re: [PATCH v3 08/18] arm/arm64: KVM: Add PSCI version selection API

On Sat, Feb 03, 2018 at 11:59:32AM +, Marc Zyngier wrote: > On Fri, 2 Feb 2018 21:17:06 +0100 > Andrew Jones wrote: > > > On Thu, Feb 01, 2018 at 11:46:47AM +, Marc Zyngier wrote: > > > Although we've implemented PSCI 1.0 and 1.1, nothing can select them > > > Since

Re: [PATCH v3 08/18] arm/arm64: KVM: Add PSCI version selection API

On Sat, Feb 03, 2018 at 11:59:32AM +, Marc Zyngier wrote: > On Fri, 2 Feb 2018 21:17:06 +0100 > Andrew Jones wrote: > > > On Thu, Feb 01, 2018 at 11:46:47AM +, Marc Zyngier wrote: > > > Although we've implemented PSCI 1.0 and 1.1, nothing can select them > > > Since all the new PSCI

Re: [PATCH v4 01/10] ufs: sysfs: attribute group for existing sysfs entries.

On Sun, Feb 04, 2018 at 12:29:06PM +, Stanislav Nijnikov wrote: > > > + curr_len += snprintf((buf + curr_len), (PAGE_SIZE - curr_len), > > > + "\nAll available Runtime PM levels info:\n"); > > > + for (lvl = UFS_PM_LVL_0; lvl < UFS_PM_LVL_MAX; lvl++) > > > +

Re: [PATCH v4 01/10] ufs: sysfs: attribute group for existing sysfs entries.

On Sun, Feb 04, 2018 at 12:29:06PM +, Stanislav Nijnikov wrote: > > > + curr_len += snprintf((buf + curr_len), (PAGE_SIZE - curr_len), > > > + "\nAll available Runtime PM levels info:\n"); > > > + for (lvl = UFS_PM_LVL_0; lvl < UFS_PM_LVL_MAX; lvl++) > > > +

RE: [PATCH v4 01/10] ufs: sysfs: attribute group for existing sysfs entries.

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Thursday, February 1, 2018 6:59 PM > To: Stanislav Nijnikov > Cc: linux-s...@vger.kernel.org; linux-kernel@vger.kernel.org; > jaeg...@kernel.org; Alex Lemberg

RE: [PATCH v4 01/10] ufs: sysfs: attribute group for existing sysfs entries.

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Thursday, February 1, 2018 6:59 PM > To: Stanislav Nijnikov > Cc: linux-s...@vger.kernel.org; linux-kernel@vger.kernel.org; > jaeg...@kernel.org; Alex Lemberg > Subject: Re: [PATCH v4 01/10] ufs: sysfs:

Re: PROBLEM: NULL pointer dereference in dell_set_arguments() in 4.15

On Sunday 04 February 2018 12:23:33 Alexander Sergeyev wrote: > Mario, > > > Would you please try https://patchwork.kernel.org/patch/10194287/ > > And see if it cleans up this null pointer dereference? > > Yes, it does. So problem which I spotted is not only theoretical, but already affects

Re: PROBLEM: NULL pointer dereference in dell_set_arguments() in 4.15

On Sunday 04 February 2018 12:23:33 Alexander Sergeyev wrote: > Mario, > > > Would you please try https://patchwork.kernel.org/patch/10194287/ > > And see if it cleans up this null pointer dereference? > > Yes, it does. So problem which I spotted is not only theoretical, but already affects

Re: [PATCH net 1/1 v1] rtnetlink: require unique netns identifier

On Sat, Feb 03, 2018 at 07:09:55PM -0700, David Ahern wrote: > On 2/3/18 12:17 PM, Stephen Hemminger wrote: > > On Sat, 3 Feb 2018 14:29:04 +0100 > > Christian Brauner wrote: > > > >> +static int rtnl_ensure_unique_netns_attr(const struct sock *sk, > >> +

Re: [PATCH net 1/1 v1] rtnetlink: require unique netns identifier

On Sat, Feb 03, 2018 at 07:09:55PM -0700, David Ahern wrote: > On 2/3/18 12:17 PM, Stephen Hemminger wrote: > > On Sat, 3 Feb 2018 14:29:04 +0100 > > Christian Brauner wrote: > > > >> +static int rtnl_ensure_unique_netns_attr(const struct sock *sk, > >> +

Re: [PATCH net 1/1 v1] rtnetlink: require unique netns identifier

On Sat, Feb 03, 2018 at 11:17:01AM -0800, Stephen Hemminger wrote: > On Sat, 3 Feb 2018 14:29:04 +0100 > Christian Brauner wrote: > > > +static int rtnl_ensure_unique_netns_attr(const struct sock *sk, > > +struct nlattr *tb[], >

Re: [PATCH net 1/1 v1] rtnetlink: require unique netns identifier

On Sat, Feb 03, 2018 at 11:17:01AM -0800, Stephen Hemminger wrote: > On Sat, 3 Feb 2018 14:29:04 +0100 > Christian Brauner wrote: > > > +static int rtnl_ensure_unique_netns_attr(const struct sock *sk, > > +struct nlattr *tb[], > > +

Re: [PATCH v2] platform/x86: dell-laptop: Allocate buffer on heap rather than globally

On Wednesday 31 January 2018 11:47:35 Mario Limonciello wrote: > There is no longer a need for the buffer to be defined in > first 4GB physical address space. > > Furthermore there may be race conditions with multiple different functions > working on a module wide buffer causing incorrect

Re: [PATCH v2] platform/x86: dell-laptop: Allocate buffer on heap rather than globally

On Wednesday 31 January 2018 11:47:35 Mario Limonciello wrote: > There is no longer a need for the buffer to be defined in > first 4GB physical address space. > > Furthermore there may be race conditions with multiple different functions > working on a module wide buffer causing incorrect

Re: [PATCH AUTOSEL for 4.14 065/110] led: core: Fix brightness setting when setting delay_off=0

On Sun, Feb 04, 2018 at 10:05:31AM +0100, Pavel Machek wrote: > On Sun 2018-02-04 00:30:36, Sasha Levin wrote: > > On Sat, Feb 03, 2018 at 09:35:26PM +0100, Pavel Machek wrote: > > >On Sat 2018-02-03 18:00:59, Sasha Levin wrote: > > >> From: Matthieu CASTET > > >> > >

Re: [PATCH AUTOSEL for 4.14 065/110] led: core: Fix brightness setting when setting delay_off=0

On Sun, Feb 04, 2018 at 10:05:31AM +0100, Pavel Machek wrote: > On Sun 2018-02-04 00:30:36, Sasha Levin wrote: > > On Sat, Feb 03, 2018 at 09:35:26PM +0100, Pavel Machek wrote: > > >On Sat 2018-02-03 18:00:59, Sasha Levin wrote: > > >> From: Matthieu CASTET > > >> > > >> [ Upstream commit

Re: [PATCH 4.14 103/156] scripts/faddr2line: extend usage on generic arch

On Sun, Feb 04, 2018 at 02:46:58PM +0800, Liu, Changcheng wrote: > Hi Greg Kroah-Hartman, > Below commit is needed to resolve issue in this patch: > Upstream commit 4cc90b4cc3d4955f79eae4f7f9d64e67e17b468e Many thanks for letting me know, I'll go queue that up. greg k-h

Re: [PATCH 4.14 103/156] scripts/faddr2line: extend usage on generic arch

On Sun, Feb 04, 2018 at 02:46:58PM +0800, Liu, Changcheng wrote: > Hi Greg Kroah-Hartman, > Below commit is needed to resolve issue in this patch: > Upstream commit 4cc90b4cc3d4955f79eae4f7f9d64e67e17b468e Many thanks for letting me know, I'll go queue that up. greg k-h

Re: [PATCH v4 02/10] ufs: sysfs: device descriptor

On Sun, Feb 04, 2018 at 09:03:25AM +, Stanislav Nijnikov wrote: > > -Original Message- > > From: Bart Van Assche > > Sent: Friday, February 2, 2018 6:32 PM > > To: gre...@linuxfoundation.org > > Cc: linux-s...@vger.kernel.org; linux-kernel@vger.kernel.org; > > jaeg...@kernel.org; Alex

Re: [PATCH v4 02/10] ufs: sysfs: device descriptor

On Sun, Feb 04, 2018 at 09:03:25AM +, Stanislav Nijnikov wrote: > > -Original Message- > > From: Bart Van Assche > > Sent: Friday, February 2, 2018 6:32 PM > > To: gre...@linuxfoundation.org > > Cc: linux-s...@vger.kernel.org; linux-kernel@vger.kernel.org; > > jaeg...@kernel.org; Alex

Re: [PATCH] staging: lustre: llite: replace variable length array

On 01/30/2018 03:04 AM, Dilger, Andreas wrote: > On Jan 27, 2018, at 14:42, Sven Dziadek wrote: >> >> The functionality of the removed variable length array is already >> implemented by the function xattr_full_name in fs/xattr.c >> >> This fixes the sparse warning: >>

Re: [PATCH] staging: lustre: llite: replace variable length array

On 01/30/2018 03:04 AM, Dilger, Andreas wrote: > On Jan 27, 2018, at 14:42, Sven Dziadek wrote: >> >> The functionality of the removed variable length array is already >> implemented by the function xattr_full_name in fs/xattr.c >> >> This fixes the sparse warning: >> warning: Variable length

Re: [PATCH] hid-sensor-accel-3d: Delete an error message for a failed memory allocation in hid_accel_3d_probe()

On Wed, 31 Jan 2018 22:26:14 +0100 SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 31 Jan 2018 22:20:56 +0100 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by

Re: [PATCH] hid-sensor-accel-3d: Delete an error message for a failed memory allocation in hid_accel_3d_probe()

On Wed, 31 Jan 2018 22:26:14 +0100 SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 31 Jan 2018 22:20:56 +0100 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus

Re: [PATCH] iio: srf08: fix link error "devm_iio_triggered_buffer_setup" undefined

On Thu, 1 Feb 2018 21:49:24 +0100 Andreas Klinger wrote: > Functions for triggered buffer support are needed by this module. > If they are not defined accidentally by another driver, there's an error > thrown out while linking. > > Add a select of IIO_BUFFER and

Re: [PATCH] iio: srf08: fix link error "devm_iio_triggered_buffer_setup" undefined

On Thu, 1 Feb 2018 21:49:24 +0100 Andreas Klinger wrote: > Functions for triggered buffer support are needed by this module. > If they are not defined accidentally by another driver, there's an error > thrown out while linking. > > Add a select of IIO_BUFFER and IIO_TRIGGERED_BUFFER in the

Re: Linux 4.15.1

diff --git a/Makefile b/Makefile index c8b8e902d5a4..af101b556ba0 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ # SPDX-License-Identifier: GPL-2.0 VERSION = 4 PATCHLEVEL = 15 -SUBLEVEL = 0 +SUBLEVEL = 1 EXTRAVERSION = NAME = Fearless Coyote diff --git

Re: Linux 4.15.1

diff --git a/Makefile b/Makefile index c8b8e902d5a4..af101b556ba0 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ # SPDX-License-Identifier: GPL-2.0 VERSION = 4 PATCHLEVEL = 15 -SUBLEVEL = 0 +SUBLEVEL = 1 EXTRAVERSION = NAME = Fearless Coyote diff --git

Linux 4.15.1

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

Linux 4.15.1

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

Linux 4.14.17

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

Re: scsi: sg: assorted memory corruptions

On Sun, Feb 4, 2018 at 10:07 AM, Eric Biggers wrote: > On Thu, Feb 01, 2018 at 05:21:12PM +0100, 'Dmitry Vyukov' via syzkaller wrote: >> On Thu, Feb 1, 2018 at 5:17 PM, Ben Hutchings >> wrote: >> > On Thu, 2018-02-01 at 08:04 +0100, Dmitry

Re: scsi: sg: assorted memory corruptions

On Sun, Feb 4, 2018 at 10:07 AM, Eric Biggers wrote: > On Thu, Feb 01, 2018 at 05:21:12PM +0100, 'Dmitry Vyukov' via syzkaller wrote: >> On Thu, Feb 1, 2018 at 5:17 PM, Ben Hutchings >> wrote: >> > On Thu, 2018-02-01 at 08:04 +0100, Dmitry Vyukov wrote: >> >> On Thu, Feb 1, 2018 at 7:03 AM,

Linux 4.14.17

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

Linux 4.9.80

I'm announcing the release of the 4.9.80 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.80

I'm announcing the release of the 4.9.80 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: Linux 4.9.80

diff --git a/Makefile b/Makefile index 4a7e6dff1c2e..9550b6939076 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 9 -SUBLEVEL = 79 +SUBLEVEL = 80 EXTRAVERSION = NAME = Roaring Lionus diff --git a/arch/arm/boot/dts/bcm-nsp.dtsi b/arch/arm/boot/dts/bcm-nsp.dtsi

Re: [PATCH v4] Staging: iio: ade7758: Expand buf_lock to cover both buffer and state protection

On Sat, 3 Feb 2018 21:01:32 +0530 Shreeya Patel wrote: > iio_dev->mlock is to be used only by the IIO core for protecting > device mode changes between INDIO_DIRECT and INDIO_BUFFER. > > This patch replaces the use of mlock with the already established > buf_lock

Re: [PATCH v4] Staging: iio: ade7758: Expand buf_lock to cover both buffer and state protection

On Sat, 3 Feb 2018 21:01:32 +0530 Shreeya Patel wrote: > iio_dev->mlock is to be used only by the IIO core for protecting > device mode changes between INDIO_DIRECT and INDIO_BUFFER. > > This patch replaces the use of mlock with the already established > buf_lock mutex. > > Introducing

Re: Linux 4.9.80

diff --git a/Makefile b/Makefile index 4a7e6dff1c2e..9550b6939076 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 9 -SUBLEVEL = 79 +SUBLEVEL = 80 EXTRAVERSION = NAME = Roaring Lionus diff --git a/arch/arm/boot/dts/bcm-nsp.dtsi b/arch/arm/boot/dts/bcm-nsp.dtsi

Re: Linux 4.4.115

diff --git a/Makefile b/Makefile index 153440b1bbb0..9c60120dd9fd 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 114 +SUBLEVEL = 115 EXTRAVERSION = NAME = Blurry Fish Butt diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index

Re: Linux 4.4.115

diff --git a/Makefile b/Makefile index 153440b1bbb0..9c60120dd9fd 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 114 +SUBLEVEL = 115 EXTRAVERSION = NAME = Blurry Fish Butt diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index

Linux 4.4.115

I'm announcing the release of the 4.4.115 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.115

I'm announcing the release of the 4.4.115 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:

Re: [PATCH] iio/orientation: Delete an error message for a failed memory allocation in two functions

On Mon, 29 Jan 2018 22:26:15 +0100 SF Markus Elfring wrote: > From: Markus Elfring > Date: Mon, 29 Jan 2018 22:20:07 +0100 > > Omit an extra message for a memory allocation failure in these functions. > > This issue was detected by

Re: [PATCH] iio/orientation: Delete an error message for a failed memory allocation in two functions

On Mon, 29 Jan 2018 22:26:15 +0100 SF Markus Elfring wrote: > From: Markus Elfring > Date: Mon, 29 Jan 2018 22:20:07 +0100 > > Omit an extra message for a memory allocation failure in these functions. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus

Re: [PATCH] iio/pressure: Delete an error message for a failed memory allocation in hid_press_probe()

On Mon, 29 Jan 2018 22:04:11 +0100 SF Markus Elfring wrote: > From: Markus Elfring > Date: Mon, 29 Jan 2018 21:55:08 +0100 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by

Re: [PATCH] iio/pressure: Delete an error message for a failed memory allocation in hid_press_probe()

On Mon, 29 Jan 2018 22:04:11 +0100 SF Markus Elfring wrote: > From: Markus Elfring > Date: Mon, 29 Jan 2018 21:55:08 +0100 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus

Re: possible deadlock in rtnl_lock (2)

On Sat, Feb 3, 2018 at 12:25 PM, Xin Long wrote: > On Thu, Feb 1, 2018 at 7:58 PM, syzbot > wrote: >> Hello, >> >> syzbot hit the following crash on upstream commit >> 255442c93843f52b6891b21d0b485bf2c97f93c3 (Thu Feb 1

Re: possible deadlock in rtnl_lock (2)

On Sat, Feb 3, 2018 at 12:25 PM, Xin Long wrote: > On Thu, Feb 1, 2018 at 7:58 PM, syzbot > wrote: >> Hello, >> >> syzbot hit the following crash on upstream commit >> 255442c93843f52b6891b21d0b485bf2c97f93c3 (Thu Feb 1 03:25:25 2018 +) >> Merge tag 'docs-4.16' of git://git.lwn.net/linux >>

[RFC 3/3] seccomp: add a way to get a listener fd from ptrace

As an alternative to SECCOMP_FILTER_FLAG_GET_LISTENER, perhaps a ptrace() version which can acquire filters is useful. There are at least two reasons this is preferable, even though it uses ptrace: 1. You can control tasks that aren't cooperating with you 2. You can control tasks whose filters

[RFC 3/3] seccomp: add a way to get a listener fd from ptrace

As an alternative to SECCOMP_FILTER_FLAG_GET_LISTENER, perhaps a ptrace() version which can acquire filters is useful. There are at least two reasons this is preferable, even though it uses ptrace: 1. You can control tasks that aren't cooperating with you 2. You can control tasks whose filters

[RFC 2/3] seccomp: hoist out filter resolving logic

Hoist out the nth filter resolving logic that ptrace uses into a new function. We'll use this in the next patch to implement the new PTRACE_SECCOMP_GET_FILTER_FLAGS command. This is based on an older patch that I had sent a while ago; it significantly revamps the get_nth_filter logic based on

[RFC 0/3] seccomp trap to userspace

Several months ago at Linux Plumber's, we had a discussion about adding a feature to seccomp which would allow seccomp to trigger a notification for some other process. Here's a draft of that feature. Patch 1 contains the bulk of it, patches 2 & 3 offer an alternative way to acquire the fd that

[RFC 2/3] seccomp: hoist out filter resolving logic

Hoist out the nth filter resolving logic that ptrace uses into a new function. We'll use this in the next patch to implement the new PTRACE_SECCOMP_GET_FILTER_FLAGS command. This is based on an older patch that I had sent a while ago; it significantly revamps the get_nth_filter logic based on

[RFC 0/3] seccomp trap to userspace

Several months ago at Linux Plumber's, we had a discussion about adding a feature to seccomp which would allow seccomp to trigger a notification for some other process. Here's a draft of that feature. Patch 1 contains the bulk of it, patches 2 & 3 offer an alternative way to acquire the fd that

[RFC 1/3] seccomp: add a return code to trap to userspace

This patch introduces a means for syscalls matched in seccomp to notify some other task that a particular filter has been triggered. The motivation for this is primarily for use with containers. For example, if a container does an init_module(), we obviously don't want to load this untrusted

[RFC 1/3] seccomp: add a return code to trap to userspace

This patch introduces a means for syscalls matched in seccomp to notify some other task that a particular filter has been triggered. The motivation for this is primarily for use with containers. For example, if a container does an init_module(), we obviously don't want to load this untrusted

Re: [PATCH 5/5] lightnvm: pblk: refactor bad block identification

> On 31 Jan 2018, at 19.24, Matias Bjørling wrote: > > On 01/31/2018 10:13 AM, Javier Gonzalez wrote: >>> On 31 Jan 2018, at 16.51, Matias Bjørling wrote: >>> >> I have a patches abstracting this, which I think it makes it cleaner. I can >> push it next

Re: [PATCH 5/5] lightnvm: pblk: refactor bad block identification

> On 31 Jan 2018, at 19.24, Matias Bjørling wrote: > > On 01/31/2018 10:13 AM, Javier Gonzalez wrote: >>> On 31 Jan 2018, at 16.51, Matias Bjørling wrote: >>> >> I have a patches abstracting this, which I think it makes it cleaner. I can >> push it next week for review. I’m traveling this

Re: [PATCH v13 1/3] lib: Add strongly typed 64bit int_sqrt

On Thu, 11 Jan 2018 11:19:57 +0100 Crt Mori wrote: > There is no option to perform 64bit integer sqrt on 32bit platform. > Added stronger typed int_sqrt64 enables the 64bit calculations to > be performed on 32bit platforms. Using same algorithm as int_sqrt() > with strong

Re: [PATCH v13 1/3] lib: Add strongly typed 64bit int_sqrt

On Thu, 11 Jan 2018 11:19:57 +0100 Crt Mori wrote: > There is no option to perform 64bit integer sqrt on 32bit platform. > Added stronger typed int_sqrt64 enables the 64bit calculations to > be performed on 32bit platforms. Using same algorithm as int_sqrt() > with strong typing provides enough

Re: [PATCH v12 1/3] lib: Add strongly typed 64bit int_sqrt

On Mon, 15 Jan 2018 02:36:15 -0800 Joe Perches wrote: > On Wed, 2018-01-10 at 09:37 +0100, Crt Mori wrote: > > Shouldn't I rather make it > > > > if (x <= ULONG_MAX) > > return int_sqrt((unsigned long) x); > > With this change: (I believe done in

Re: [PATCH v12 1/3] lib: Add strongly typed 64bit int_sqrt

On Mon, 15 Jan 2018 02:36:15 -0800 Joe Perches wrote: > On Wed, 2018-01-10 at 09:37 +0100, Crt Mori wrote: > > Shouldn't I rather make it > > > > if (x <= ULONG_MAX) > > return int_sqrt((unsigned long) x); > > With this change: (I believe done in v13) and > as

Re: [GIT PULL tools] Linux kernel memory model

On Sun, Feb 04, 2018 at 01:16:01AM -0800, Paul E. McKenney wrote: > On Sat, Feb 03, 2018 at 05:10:06PM -0500, Alan Stern wrote: > > On Sat, 3 Feb 2018, Paul E. McKenney wrote: > > > > > Please see below for an initial patch to this effect. This activity > > > proved to be more productive than

Re: [GIT PULL tools] Linux kernel memory model

On Sun, Feb 04, 2018 at 01:16:01AM -0800, Paul E. McKenney wrote: > On Sat, Feb 03, 2018 at 05:10:06PM -0500, Alan Stern wrote: > > On Sat, 3 Feb 2018, Paul E. McKenney wrote: > > > > > Please see below for an initial patch to this effect. This activity > > > proved to be more productive than

Re: [PATCH v3 14/21] fpga: dfl: add fpga manager platform driver for FME

On Sat, Feb 03, 2018 at 11:41:24AM +0100, Moritz Fischer wrote: > Hi Hao, > > On Fri, Feb 02, 2018 at 04:26:26PM -0800, Luebbers, Enno wrote: > > Hi Hao, Alan, > > > > On Fri, Feb 02, 2018 at 05:42:13PM +0800, Wu Hao wrote: > > > On Thu, Feb 01, 2018 at 04:00:36PM -0600, Alan Tull wrote: > > > >

Re: [PATCH v3 14/21] fpga: dfl: add fpga manager platform driver for FME

On Sat, Feb 03, 2018 at 11:41:24AM +0100, Moritz Fischer wrote: > Hi Hao, > > On Fri, Feb 02, 2018 at 04:26:26PM -0800, Luebbers, Enno wrote: > > Hi Hao, Alan, > > > > On Fri, Feb 02, 2018 at 05:42:13PM +0800, Wu Hao wrote: > > > On Thu, Feb 01, 2018 at 04:00:36PM -0600, Alan Tull wrote: > > > >

[PATCH] tracing: Fix incorrect file name

There is no file named 'enabled' in the directory tracing/events. It should be the file 'enable'. Signed-off-by: Xiongwei Song --- Documentation/trace/events.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/trace/events.txt

[PATCH] tracing: Fix incorrect file name

There is no file named 'enabled' in the directory tracing/events. It should be the file 'enable'. Signed-off-by: Xiongwei Song --- Documentation/trace/events.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/trace/events.txt b/Documentation/trace/events.txt

Re: [PATCH 2/2] MAINTAINERS: list file memory-barriers.txt within the LKMM entry

On Sat, Feb 03, 2018 at 02:08:00AM +0100, Andrea Parri wrote: > On Fri, Feb 02, 2018 at 03:51:02PM -0800, Paul E. McKenney wrote: > > On Fri, Feb 02, 2018 at 10:13:42AM +0100, Andrea Parri wrote: > > > Now that a formal specification of the LKMM has become available to > > > the developer, some

Re: [PATCH 2/2] MAINTAINERS: list file memory-barriers.txt within the LKMM entry

On Sat, Feb 03, 2018 at 02:08:00AM +0100, Andrea Parri wrote: > On Fri, Feb 02, 2018 at 03:51:02PM -0800, Paul E. McKenney wrote: > > On Fri, Feb 02, 2018 at 10:13:42AM +0100, Andrea Parri wrote: > > > Now that a formal specification of the LKMM has become available to > > > the developer, some

Re: Compilation error report for: drivers/firmware/qcom_scm.c:469:47: error: passing argument 3 of ?dma_alloc_coherent? from incompatible pointer type

2018-02-03 0:29 GMT+01:00 Bjorn Andersson : > On Tue 30 Jan 05:25 PST 2018, Arnd Bergmann wrote: > >> On Tue, Jan 30, 2018 at 11:11 AM, Benjamin GAIGNARD >> wrote: >> > >> > On 01/12/2018 05:11 PM, Arnaud Pouliquen wrote: >> >> Hello

Re: Compilation error report for: drivers/firmware/qcom_scm.c:469:47: error: passing argument 3 of ?dma_alloc_coherent? from incompatible pointer type

2018-02-03 0:29 GMT+01:00 Bjorn Andersson : > On Tue 30 Jan 05:25 PST 2018, Arnd Bergmann wrote: > >> On Tue, Jan 30, 2018 at 11:11 AM, Benjamin GAIGNARD >> wrote: >> > >> > On 01/12/2018 05:11 PM, Arnaud Pouliquen wrote: >> >> Hello Andy,David, >> > + Arnd >> > >> > I have the same issue on

[PATCH] Fix a typo in Documentation/sysctl/user.txt

A trivial patch to fix a typo in Documentation/sysctl/user.txt Fix 'documetation' to 'documentation' Signed-off-by: Kangmin Park Cc: Jiri Kosina Cc: Andrew Morton diff --git a/Documentation/sysctl/user.txt

[PATCH] Fix a typo in Documentation/sysctl/user.txt

A trivial patch to fix a typo in Documentation/sysctl/user.txt Fix 'documetation' to 'documentation' Signed-off-by: Kangmin Park Cc: Jiri Kosina Cc: Andrew Morton diff --git a/Documentation/sysctl/user.txt b/Documentation/sysctl/user.txt index 1291c49..a588286 100644 ---

Re: [PATCH v3 14/21] fpga: dfl: add fpga manager platform driver for FME

On Fri, Feb 02, 2018 at 04:26:26PM -0800, Luebbers, Enno wrote: > Hi Hao, Alan, > > On Fri, Feb 02, 2018 at 05:42:13PM +0800, Wu Hao wrote: > > On Thu, Feb 01, 2018 at 04:00:36PM -0600, Alan Tull wrote: > > > On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote: > > > > > > Hi Hao,

Re: [PATCH v3 14/21] fpga: dfl: add fpga manager platform driver for FME

On Fri, Feb 02, 2018 at 04:26:26PM -0800, Luebbers, Enno wrote: > Hi Hao, Alan, > > On Fri, Feb 02, 2018 at 05:42:13PM +0800, Wu Hao wrote: > > On Thu, Feb 01, 2018 at 04:00:36PM -0600, Alan Tull wrote: > > > On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote: > > > > > > Hi Hao, > > > > > > A few

Re: PROBLEM: NULL pointer dereference in dell_set_arguments() in 4.15

Mario, Would you please try https://patchwork.kernel.org/patch/10194287/ And see if it cleans up this null pointer dereference? Yes, it does. Is there any estimates on when the patch will be merged into mainline? I want to put something into my distribution bug tracker, but it's unlikely

Re: PROBLEM: NULL pointer dereference in dell_set_arguments() in 4.15

Mario, Would you please try https://patchwork.kernel.org/patch/10194287/ And see if it cleans up this null pointer dereference? Yes, it does. Is there any estimates on when the patch will be merged into mainline? I want to put something into my distribution bug tracker, but it's unlikely

Re: [PATCH] Revert "cpuidle: Make drivers initialize polling state"

On Sun, Feb 4, 2018 at 10:12 AM, Rafael J. Wysocki wrote: > On Mon, Jan 22, 2018 at 5:27 PM, Ville Syrjala > wrote: >> From: Ville Syrjälä >> >> This reverts commit 1b39e3f813b4685c7a30ae964d5529a1b0e3a286. >> >>

Re: [PATCH] Revert "cpuidle: Make drivers initialize polling state"

On Sun, Feb 4, 2018 at 10:12 AM, Rafael J. Wysocki wrote: > On Mon, Jan 22, 2018 at 5:27 PM, Ville Syrjala > wrote: >> From: Ville Syrjälä >> >> This reverts commit 1b39e3f813b4685c7a30ae964d5529a1b0e3a286. >> >> Makes my P3 machine oops somewhere in cpuidle. I suspect >> CONFIG_ACPI=n may have

Re: [GIT PULL tools] Linux kernel memory model

On Sat, Feb 03, 2018 at 05:10:06PM -0500, Alan Stern wrote: > On Sat, 3 Feb 2018, Paul E. McKenney wrote: > > > Please see below for an initial patch to this effect. This activity > > proved to be more productive than expected for these tests, which certainly > > supports our assertion that

Re: [GIT PULL tools] Linux kernel memory model

On Sat, Feb 03, 2018 at 05:10:06PM -0500, Alan Stern wrote: > On Sat, 3 Feb 2018, Paul E. McKenney wrote: > > > Please see below for an initial patch to this effect. This activity > > proved to be more productive than expected for these tests, which certainly > > supports our assertion that

Re: [PATCH] Revert "cpuidle: Make drivers initialize polling state"

On Mon, Jan 22, 2018 at 5:27 PM, Ville Syrjala wrote: > From: Ville Syrjälä > > This reverts commit 1b39e3f813b4685c7a30ae964d5529a1b0e3a286. > > Makes my P3 machine oops somewhere in cpuidle. I suspect > CONFIG_ACPI=n may have

Re: [PATCH] Revert "cpuidle: Make drivers initialize polling state"

On Mon, Jan 22, 2018 at 5:27 PM, Ville Syrjala wrote: > From: Ville Syrjälä > > This reverts commit 1b39e3f813b4685c7a30ae964d5529a1b0e3a286. > > Makes my P3 machine oops somewhere in cpuidle. I suspect > CONFIG_ACPI=n may have something to do with this. And if you don't do CONFIG_ACPI=n, does

Re: scsi: sg: assorted memory corruptions

On Thu, Feb 01, 2018 at 05:21:12PM +0100, 'Dmitry Vyukov' via syzkaller wrote: > On Thu, Feb 1, 2018 at 5:17 PM, Ben Hutchings > wrote: > > On Thu, 2018-02-01 at 08:04 +0100, Dmitry Vyukov wrote: > >> On Thu, Feb 1, 2018 at 7:03 AM, Douglas Gilbert

Re: scsi: sg: assorted memory corruptions

On Thu, Feb 01, 2018 at 05:21:12PM +0100, 'Dmitry Vyukov' via syzkaller wrote: > On Thu, Feb 1, 2018 at 5:17 PM, Ben Hutchings > wrote: > > On Thu, 2018-02-01 at 08:04 +0100, Dmitry Vyukov wrote: > >> On Thu, Feb 1, 2018 at 7:03 AM, Douglas Gilbert > >> wrote: > >> > On 2018-01-30 07:22 AM,

Re: [PATCH AUTOSEL for 4.14 065/110] led: core: Fix brightness setting when setting delay_off=0

On Sun 2018-02-04 00:30:36, Sasha Levin wrote: > On Sat, Feb 03, 2018 at 09:35:26PM +0100, Pavel Machek wrote: > >On Sat 2018-02-03 18:00:59, Sasha Levin wrote: > >> From: Matthieu CASTET > >> > >> [ Upstream commit 2b83ff96f51d0b039c4561b9f95c824d7bddb85c ] > >> > >>

Re: [PATCH AUTOSEL for 4.14 065/110] led: core: Fix brightness setting when setting delay_off=0

On Sun 2018-02-04 00:30:36, Sasha Levin wrote: > On Sat, Feb 03, 2018 at 09:35:26PM +0100, Pavel Machek wrote: > >On Sat 2018-02-03 18:00:59, Sasha Levin wrote: > >> From: Matthieu CASTET > >> > >> [ Upstream commit 2b83ff96f51d0b039c4561b9f95c824d7bddb85c ] > >> > >> With the current code, the

RE: [PATCH v4 02/10] ufs: sysfs: device descriptor

> -Original Message- > From: Bart Van Assche > Sent: Friday, February 2, 2018 6:32 PM > To: gre...@linuxfoundation.org > Cc: linux-s...@vger.kernel.org; linux-kernel@vger.kernel.org; > jaeg...@kernel.org; Alex Lemberg ; Stanislav > Nijnikov

RE: [PATCH v4 02/10] ufs: sysfs: device descriptor

> -Original Message- > From: Bart Van Assche > Sent: Friday, February 2, 2018 6:32 PM > To: gre...@linuxfoundation.org > Cc: linux-s...@vger.kernel.org; linux-kernel@vger.kernel.org; > jaeg...@kernel.org; Alex Lemberg ; Stanislav > Nijnikov > Subject: Re: [PATCH v4 02/10] ufs: sysfs:

Re: [PATCH] ACPI/PCI: pci_link: reduce verbosity when IRQ is enabled

On Thu, Feb 1, 2018 at 8:32 AM, Rafael J. Wysocki wrote: > On Mon, Jan 29, 2018 at 8:01 PM, Sinan Kaya wrote: >> Rafael, >> >> On 1/16/2018 4:49 PM, Bjorn Helgaas wrote: >>> On Tue, Jan 16, 2018 at 01:53:00PM -0500, Sinan Kaya wrote: Correcting

Re: [PATCH] ACPI/PCI: pci_link: reduce verbosity when IRQ is enabled

On Thu, Feb 1, 2018 at 8:32 AM, Rafael J. Wysocki wrote: > On Mon, Jan 29, 2018 at 8:01 PM, Sinan Kaya wrote: >> Rafael, >> >> On 1/16/2018 4:49 PM, Bjorn Helgaas wrote: >>> On Tue, Jan 16, 2018 at 01:53:00PM -0500, Sinan Kaya wrote: Correcting linux-pci email. On 1/16/2018 1:51

Re: [PATCH v1 1/3] ACPI / x86: boot: Not all platforms require acpi_reduced_hw_init()

On Wednesday, January 17, 2018 6:34:07 PM CET Andy Shevchenko wrote: > Some platforms might take care of legacy devices on theirs own. > Let's allow them to do that by exporting a weak function. > > Signed-off-by: Andy Shevchenko > --- >

Re: [PATCH v1 1/3] ACPI / x86: boot: Not all platforms require acpi_reduced_hw_init()

On Wednesday, January 17, 2018 6:34:07 PM CET Andy Shevchenko wrote: > Some platforms might take care of legacy devices on theirs own. > Let's allow them to do that by exporting a weak function. > > Signed-off-by: Andy Shevchenko > --- > arch/x86/kernel/acpi/boot.c | 2 +- >

Re: [PATCH 4/4] sched/fair: Use a recently used CPU as an idle candidate and the basis for SIS

On Friday, February 2, 2018 8:48:01 PM CET Mel Gorman wrote: > On Fri, Feb 02, 2018 at 06:54:24AM -0800, Srinivas Pandruvada wrote: > > > > > No idea, desired would be the one I would start with, it matches > > > > > with > > > > > the intent here. But I've no idea what our current HWP > > > > >

Re: [PATCH 4/4] sched/fair: Use a recently used CPU as an idle candidate and the basis for SIS

On Friday, February 2, 2018 8:48:01 PM CET Mel Gorman wrote: > On Fri, Feb 02, 2018 at 06:54:24AM -0800, Srinivas Pandruvada wrote: > > > > > No idea, desired would be the one I would start with, it matches > > > > > with > > > > > the intent here. But I've no idea what our current HWP > > > > >

Re: [PATCH 4/4] sched/fair: Use a recently used CPU as an idle candidate and the basis for SIS

On Friday, February 2, 2018 3:54:24 PM CET Srinivas Pandruvada wrote: > On Fri, 2018-02-02 at 12:00 +0100, Rafael J. Wysocki wrote: > > On Thursday, February 1, 2018 2:18:12 PM CET Srinivas Pandruvada > > wrote: > > > > > > On Thu, 2018-02-01 at 10:11 +0100, Peter Zijlstra wrote: > > > > > > > >

Re: [PATCH 4/4] sched/fair: Use a recently used CPU as an idle candidate and the basis for SIS

On Friday, February 2, 2018 3:54:24 PM CET Srinivas Pandruvada wrote: > On Fri, 2018-02-02 at 12:00 +0100, Rafael J. Wysocki wrote: > > On Thursday, February 1, 2018 2:18:12 PM CET Srinivas Pandruvada > > wrote: > > > > > > On Thu, 2018-02-01 at 10:11 +0100, Peter Zijlstra wrote: > > > > > > > >

<    3   4   5   6   7   8   9   >