Re: [PATCH resend] mm/page_alloc: fix comment is __get_free_pages

On Thu, 30 Nov 2017 07:53:35 +0100 Michal Hocko wrote: > > mm... So we have a caller which hopes to be getting highmem pages but > > isn't. Caller then proceeds to pointlessly kmap the page and wonders > > why it isn't getting as much memory as it would like on 32-bit

Re: [PATCH resend] mm/page_alloc: fix comment is __get_free_pages

On Thu, 30 Nov 2017 07:53:35 +0100 Michal Hocko wrote: > > mm... So we have a caller which hopes to be getting highmem pages but > > isn't. Caller then proceeds to pointlessly kmap the page and wonders > > why it isn't getting as much memory as it would like on 32-bit systems, > > etc. > >

Re: [PATCH] mtd: nand: gpmi: replace _manual_ swap with swap macro

On Fri, 3 Nov 2017 15:31:47 -0500 "Gustavo A. R. Silva" wrote: > Make use of the swap macro and remove unnecessary variables swap. > This makes the code easier to read and maintain. > > This code was detected with the help of Coccinelle. Applied. Thanks, Boris > >

Re: [PATCH] mtd: nand: gpmi: replace _manual_ swap with swap macro

On Fri, 3 Nov 2017 15:31:47 -0500 "Gustavo A. R. Silva" wrote: > Make use of the swap macro and remove unnecessary variables swap. > This makes the code easier to read and maintain. > > This code was detected with the help of Coccinelle. Applied. Thanks, Boris > > Signed-off-by: Gustavo A.

Re: [RFC] Rebasing the IDR

On Thu, Nov 30, 2017 at 08:56:43PM +0100, Daniel Vetter wrote: > Adding dri-devel, I think a pile of those are in drm. Yeah, quite a lot! This is a good thing; means you didn't invent your own custom ID allocator. > On Thu, Nov 30, 2017 at 6:36 PM, Matthew Wilcox wrote: >

Re: [RFC] Rebasing the IDR

On Thu, Nov 30, 2017 at 08:56:43PM +0100, Daniel Vetter wrote: > Adding dri-devel, I think a pile of those are in drm. Yeah, quite a lot! This is a good thing; means you didn't invent your own custom ID allocator. > On Thu, Nov 30, 2017 at 6:36 PM, Matthew Wilcox wrote: > > About 40 of the

Re: [PATCH 00/11] fs: use freeze_fs on suspend/hibernate

On Thu, Nov 30, 2017 at 08:53:52PM +, Bart Van Assche wrote: > On Thu, 2017-11-30 at 20:42 +0100, Luis R. Rodriguez wrote: > > On Thu, Nov 30, 2017 at 05:01:13PM +, Bart Van Assche wrote: > > > The md resync > > > thread must be stopped before a system is frozen. Today the md driver uses >

Re: [PATCH 00/11] fs: use freeze_fs on suspend/hibernate

On Thu, Nov 30, 2017 at 08:53:52PM +, Bart Van Assche wrote: > On Thu, 2017-11-30 at 20:42 +0100, Luis R. Rodriguez wrote: > > On Thu, Nov 30, 2017 at 05:01:13PM +, Bart Van Assche wrote: > > > The md resync > > > thread must be stopped before a system is frozen. Today the md driver uses >

Re: Creating cyclecounter and lock member in timecounter structure [ Was Re: [RFC 1/4] drm/i915/perf: Add support to correlate GPU timestamp with system time]

On Mon, Nov 27, 2017 at 2:05 AM, Sagar Arun Kamble wrote: > > > On 11/24/2017 7:01 PM, Thomas Gleixner wrote: >> >> On Fri, 24 Nov 2017, Sagar Arun Kamble wrote: >>> >>> On 11/24/2017 12:29 AM, Thomas Gleixner wrote: On Thu, 23 Nov 2017, Sagar Arun Kamble

Re: Creating cyclecounter and lock member in timecounter structure [ Was Re: [RFC 1/4] drm/i915/perf: Add support to correlate GPU timestamp with system time]

On Mon, Nov 27, 2017 at 2:05 AM, Sagar Arun Kamble wrote: > > > On 11/24/2017 7:01 PM, Thomas Gleixner wrote: >> >> On Fri, 24 Nov 2017, Sagar Arun Kamble wrote: >>> >>> On 11/24/2017 12:29 AM, Thomas Gleixner wrote: On Thu, 23 Nov 2017, Sagar Arun Kamble wrote: > > We needed

[PATCH] NFS: allow name_to_handle_at() to work for Amazon EFS.

Amazon EFS provides an NFSv4.1 filesystem which appears to use (close to) full length (128 byte) file handles. This causes the handle reported by name_to_handle_at() to exceed MAX_HANDLE_SZ, resulting in EOVERFLOW if 128 bytes were requested, or EINVAL if the size reported by the previous

[PATCH] NFS: allow name_to_handle_at() to work for Amazon EFS.

Amazon EFS provides an NFSv4.1 filesystem which appears to use (close to) full length (128 byte) file handles. This causes the handle reported by name_to_handle_at() to exceed MAX_HANDLE_SZ, resulting in EOVERFLOW if 128 bytes were requested, or EINVAL if the size reported by the previous

Re: [PATCH] list_lru: Prefetch neighboring list entries before acquiring lock

On 11/30/2017 03:38 PM, Dave Chinner wrote: > On Thu, Nov 30, 2017 at 08:54:04AM -0500, Waiman Long wrote: >> >> For the record, I add one more list_empty() check at the beginning of >> list_lru_del() in the patch for 2 purpose: >> 1. it allows the code to bail out early. > Which is what I said

Re: [PATCH] list_lru: Prefetch neighboring list entries before acquiring lock

On 11/30/2017 03:38 PM, Dave Chinner wrote: > On Thu, Nov 30, 2017 at 08:54:04AM -0500, Waiman Long wrote: >> >> For the record, I add one more list_empty() check at the beginning of >> list_lru_del() in the patch for 2 purpose: >> 1. it allows the code to bail out early. > Which is what I said

[PATCH] KEYS: reject NULL restriction string when type is specified

From: Eric Biggers keyctl_restrict_keyring() allows through a NULL restriction when the "type" is non-NULL, which causes a NULL pointer dereference in asymmetric_lookup_restriction() when it calls strcmp() on the restriction string. But no key types actually use a "NULL

Re: [PATCH 00/11] fs: use freeze_fs on suspend/hibernate

On Thu, 2017-11-30 at 20:42 +0100, Luis R. Rodriguez wrote: > On Thu, Nov 30, 2017 at 05:01:13PM +, Bart Van Assche wrote: > > The md resync > > thread must be stopped before a system is frozen. Today the md driver uses > > the kthread freezing mechanism for that purpose. Do you have a plan

[PATCH] KEYS: reject NULL restriction string when type is specified

From: Eric Biggers keyctl_restrict_keyring() allows through a NULL restriction when the "type" is non-NULL, which causes a NULL pointer dereference in asymmetric_lookup_restriction() when it calls strcmp() on the restriction string. But no key types actually use a "NULL restriction" to mean

Re: [PATCH 00/11] fs: use freeze_fs on suspend/hibernate

On Thu, 2017-11-30 at 20:42 +0100, Luis R. Rodriguez wrote: > On Thu, Nov 30, 2017 at 05:01:13PM +, Bart Van Assche wrote: > > The md resync > > thread must be stopped before a system is frozen. Today the md driver uses > > the kthread freezing mechanism for that purpose. Do you have a plan

Re: waitqueue lockdep annotation

On Thu, 30 Nov 2017 06:20:35 -0800 Christoph Hellwig wrote: > Hi all, > > this series adds a strategic lockdep_assert_held to __wake_up_common > to ensure callers really do hold the wait_queue_head lock when calling > the unlocked wake_up variants. It turns out epoll did not do

Re: waitqueue lockdep annotation

On Thu, 30 Nov 2017 06:20:35 -0800 Christoph Hellwig wrote: > Hi all, > > this series adds a strategic lockdep_assert_held to __wake_up_common > to ensure callers really do hold the wait_queue_head lock when calling > the unlocked wake_up variants. It turns out epoll did not do this > for a

Re: [PATCH v2 2/2] cros_ec: Move cros_ec_dev module to drivers/mfd

On Mon, Nov 20, 2017 at 8:15 AM, Thierry Escande wrote: > The cros_ec_dev module is responsible for registering the MFD devices > attached to the ChromeOS EC. This patch moves this module to drivers/mfd > so calls to mfd_add_devices() are not done from outside the

Re: [PATCH v2 2/2] cros_ec: Move cros_ec_dev module to drivers/mfd

On Mon, Nov 20, 2017 at 8:15 AM, Thierry Escande wrote: > The cros_ec_dev module is responsible for registering the MFD devices > attached to the ChromeOS EC. This patch moves this module to drivers/mfd > so calls to mfd_add_devices() are not done from outside the MFD subtree > anymore. > >

Re: [PATCH v2 1/2] cros_ec: Split cros_ec_devs module

On Mon, Nov 20, 2017 at 8:15 AM, Thierry Escande wrote: > This patch splits the cros_ec_devs module in two parts with a > cros_ec_dev module responsible for handling MFD devices registration and > a cros_ec_ctl module responsible for handling the various user-space

Re: [PATCH v2 1/2] cros_ec: Split cros_ec_devs module

On Mon, Nov 20, 2017 at 8:15 AM, Thierry Escande wrote: > This patch splits the cros_ec_devs module in two parts with a > cros_ec_dev module responsible for handling MFD devices registration and > a cros_ec_ctl module responsible for handling the various user-space > interfaces. > > For

Re: [PATCH] list_lru: Prefetch neighboring list entries before acquiring lock

On 11/30/2017 03:47 PM, Andrew Morton wrote: > On Thu, 30 Nov 2017 08:54:04 -0500 Waiman Long wrote: > >>> And, from that perspective, the racy shortcut in the proposed patch >>> is wrong, too. Prefetch is fine, but in general shortcutting list >>> empty checks outside the

Re: [PATCH] list_lru: Prefetch neighboring list entries before acquiring lock

On 11/30/2017 03:47 PM, Andrew Morton wrote: > On Thu, 30 Nov 2017 08:54:04 -0500 Waiman Long wrote: > >>> And, from that perspective, the racy shortcut in the proposed patch >>> is wrong, too. Prefetch is fine, but in general shortcutting list >>> empty checks outside the internal lock isn't. >>

Re: [PATCH] list_lru: Prefetch neighboring list entries before acquiring lock

On Thu, 30 Nov 2017 08:54:04 -0500 Waiman Long wrote: > > And, from that perspective, the racy shortcut in the proposed patch > > is wrong, too. Prefetch is fine, but in general shortcutting list > > empty checks outside the internal lock isn't. > > For the record, I add one

Re: [PATCH] list_lru: Prefetch neighboring list entries before acquiring lock

On Thu, 30 Nov 2017 08:54:04 -0500 Waiman Long wrote: > > And, from that perspective, the racy shortcut in the proposed patch > > is wrong, too. Prefetch is fine, but in general shortcutting list > > empty checks outside the internal lock isn't. > > For the record, I add one more list_empty()

Re: BUG: sleeping function called from invalid context at arch/x86/mm/fault.c:LINE

On Thu, Nov 30, 2017 at 11:55:00AM -0800, syzbot wrote: > Call Trace: > __dump_stack lib/dump_stack.c:17 [inline] > dump_stack+0x194/0x257 lib/dump_stack.c:53 > ___might_sleep+0x2b2/0x470 kernel/sched/core.c:6060 > __might_sleep+0x95/0x190 kernel/sched/core.c:6013 >

Re: BUG: sleeping function called from invalid context at arch/x86/mm/fault.c:LINE

On Thu, Nov 30, 2017 at 11:55:00AM -0800, syzbot wrote: > Call Trace: > __dump_stack lib/dump_stack.c:17 [inline] > dump_stack+0x194/0x257 lib/dump_stack.c:53 > ___might_sleep+0x2b2/0x470 kernel/sched/core.c:6060 > __might_sleep+0x95/0x190 kernel/sched/core.c:6013 >

Re: [PATCH 2/2] kvm: x86: fix KVM_XEN_HVM_CONFIG ioctl

On Thu, Oct 26, 2017 at 6:45 AM, Paolo Bonzini wrote: > This ioctl is obsolete (it was used by Xenner as far as I know) but > still let's not break it gratuitously... Its handler is copying > directly into struct kvm. Go through a bounce buffer instead, with > the added

Re: [PATCH 2/2] kvm: x86: fix KVM_XEN_HVM_CONFIG ioctl

On Thu, Oct 26, 2017 at 6:45 AM, Paolo Bonzini wrote: > This ioctl is obsolete (it was used by Xenner as far as I know) but > still let's not break it gratuitously... Its handler is copying > directly into struct kvm. Go through a bounce buffer instead, with > the added benefit that we can

Re: [PATCH v13 0/7] cgroup-aware OOM killer

On Thu, 30 Nov 2017 15:28:17 + Roman Gushchin wrote: > This patchset makes the OOM killer cgroup-aware. Thanks, I'll grab these. There has been controversy over this patchset, to say the least. I can't say that I followed it closely! Could those who still have reservations

Re: [PATCH v13 0/7] cgroup-aware OOM killer

On Thu, 30 Nov 2017 15:28:17 + Roman Gushchin wrote: > This patchset makes the OOM killer cgroup-aware. Thanks, I'll grab these. There has been controversy over this patchset, to say the least. I can't say that I followed it closely! Could those who still have reservations please

Re: [PATCH] list_lru: Prefetch neighboring list entries before acquiring lock

On Thu, Nov 30, 2017 at 08:54:04AM -0500, Waiman Long wrote: > On 11/29/2017 07:42 PM, Dave Chinner wrote: > > On Wed, Nov 29, 2017 at 01:53:19PM -0800, Andrew Morton wrote: > >> On Wed, 29 Nov 2017 09:17:34 -0500 Waiman Long wrote: > >> > >>> The list_lru_del() function

Re: [PATCH] list_lru: Prefetch neighboring list entries before acquiring lock

On Thu, Nov 30, 2017 at 08:54:04AM -0500, Waiman Long wrote: > On 11/29/2017 07:42 PM, Dave Chinner wrote: > > On Wed, Nov 29, 2017 at 01:53:19PM -0800, Andrew Morton wrote: > >> On Wed, 29 Nov 2017 09:17:34 -0500 Waiman Long wrote: > >> > >>> The list_lru_del() function removes the given item

Re: [PATCH v2 19/23] firmware: add debug facility to emulate forcing sysfs fallback

On Wed, Nov 29, 2017 at 11:28:04AM +0100, Greg KH wrote: > On Mon, Nov 20, 2017 at 10:24:05AM -0800, Luis R. Rodriguez wrote: > > diff --git a/drivers/base/firmware_debug.c b/drivers/base/firmware_debug.c > > new file mode 100644 > > index ..f2817eb6f480 > > --- /dev/null > > +++

Re: [PATCH v2 19/23] firmware: add debug facility to emulate forcing sysfs fallback

On Wed, Nov 29, 2017 at 11:28:04AM +0100, Greg KH wrote: > On Mon, Nov 20, 2017 at 10:24:05AM -0800, Luis R. Rodriguez wrote: > > diff --git a/drivers/base/firmware_debug.c b/drivers/base/firmware_debug.c > > new file mode 100644 > > index ..f2817eb6f480 > > --- /dev/null > > +++

Re: [PATCH] KVM: x86: inject exceptions produced by x86_decode_insn

On Wed, Nov 29, 2017 at 04:42:16PM -0200, Eduardo Habkost wrote: > On Wed, Nov 29, 2017 at 12:44:42PM +0100, Paolo Bonzini wrote: > > On 29/11/2017 12:44, Eduardo Habkost wrote: > > > On Mon, Nov 13, 2017 at 09:32:09AM +0100, Paolo Bonzini wrote: > > >> On 13/11/2017 08:15, Wanpeng Li wrote: > >

Re: [PATCH] KVM: x86: inject exceptions produced by x86_decode_insn

On Wed, Nov 29, 2017 at 04:42:16PM -0200, Eduardo Habkost wrote: > On Wed, Nov 29, 2017 at 12:44:42PM +0100, Paolo Bonzini wrote: > > On 29/11/2017 12:44, Eduardo Habkost wrote: > > > On Mon, Nov 13, 2017 at 09:32:09AM +0100, Paolo Bonzini wrote: > > >> On 13/11/2017 08:15, Wanpeng Li wrote: > >

Re: [PATCH 07/11] xfs: remove not needed freezing calls

On Thu, Nov 30, 2017 at 5:21 PM, Jan Kara wrote: > On Wed 29-11-17 15:23:52, Luis R. Rodriguez wrote: >> This removes superflous freezer calls as they are no longer needed >> as the VFS now performs filesystem freezing/thaw if the filesystem has >> support for it. >> >> The

Re: [PATCH 07/11] xfs: remove not needed freezing calls

On Thu, Nov 30, 2017 at 5:21 PM, Jan Kara wrote: > On Wed 29-11-17 15:23:52, Luis R. Rodriguez wrote: >> This removes superflous freezer calls as they are no longer needed >> as the VFS now performs filesystem freezing/thaw if the filesystem has >> support for it. >> >> The following Coccinelle

Re: [PATCH v2 16/23] test_firmware: enable custom fallback testing on limited kernel configs

On Wed, Nov 29, 2017 at 11:22:35AM +0100, Greg KH wrote: > On Mon, Nov 20, 2017 at 10:24:02AM -0800, Luis R. Rodriguez wrote: > > When a kernel is not built with: > > > > CONFIG_HAS_FW_LOADER_USER_HELPER_FALLBACK=y > > > > We don't currently enable testing fw_fallback.sh. For kernels that > >

Re: [patches] [PATCH 3/4] RISC-V: Flush I$ when making a dirty page executable

Hi, On Mon, Nov 20, 2017 at 10:57 AM, Palmer Dabbelt wrote: > From: Andrew Waterman > > The RISC-V ISA allows for instruction caches that are not coherent WRT > stores, even on a single hart. As a result, we need to explicitly flush > the instruction cache

Re: [PATCH v2 16/23] test_firmware: enable custom fallback testing on limited kernel configs

On Wed, Nov 29, 2017 at 11:22:35AM +0100, Greg KH wrote: > On Mon, Nov 20, 2017 at 10:24:02AM -0800, Luis R. Rodriguez wrote: > > When a kernel is not built with: > > > > CONFIG_HAS_FW_LOADER_USER_HELPER_FALLBACK=y > > > > We don't currently enable testing fw_fallback.sh. For kernels that > >

Re: [patches] [PATCH 3/4] RISC-V: Flush I$ when making a dirty page executable

Hi, On Mon, Nov 20, 2017 at 10:57 AM, Palmer Dabbelt wrote: > From: Andrew Waterman > > The RISC-V ISA allows for instruction caches that are not coherent WRT > stores, even on a single hart. As a result, we need to explicitly flush > the instruction cache whenever marking a dirty page as

Re: [PATCH] dt-bindings: pinctrl: uniphier: add UniPhier pinctrl binding

On Tue, Nov 28, 2017 at 9:44 PM, Masahiro Yamada wrote: > Hi Rob, > > > 2017-11-29 0:27 GMT+09:00 Rob Herring : >> On Tue, Nov 28, 2017 at 04:49:45PM +0900, Masahiro Yamada wrote: >>> The driver has been in the tree for a while, but its binding

Re: [PATCH] dt-bindings: pinctrl: uniphier: add UniPhier pinctrl binding

On Tue, Nov 28, 2017 at 9:44 PM, Masahiro Yamada wrote: > Hi Rob, > > > 2017-11-29 0:27 GMT+09:00 Rob Herring : >> On Tue, Nov 28, 2017 at 04:49:45PM +0900, Masahiro Yamada wrote: >>> The driver has been in the tree for a while, but its binding document >>> is missing. Hence, here it is. >>> >>>

Re: [PATCH] riscv/ftrace: Add basic support

On Thu, 30 Nov 2017 16:53:35 +0800 Alan Kao wrote: > This patch contains basic ftrace support for RV64I platform. > Specifically, function tracer (HAVE_FUNCTION_TRACER), function graph > tracer (HAVE_FUNCTION_GRAPH_TRACER), and a frame pointer test >

Re: [PATCH] riscv/ftrace: Add basic support

On Thu, 30 Nov 2017 16:53:35 +0800 Alan Kao wrote: > This patch contains basic ftrace support for RV64I platform. > Specifically, function tracer (HAVE_FUNCTION_TRACER), function graph > tracer (HAVE_FUNCTION_GRAPH_TRACER), and a frame pointer test > (HAVE_FUNCTION_GRAPH_FP_TEST) are implemented

Re: [patches] Re: [PATCH 08/10] RISC-V: Set __ARCH_WANT_RENAMEAT to pick up generic version

On Thu, Nov 30, 2017 at 10:38 AM, Palmer Dabbelt wrote: > On Thu, 30 Nov 2017 10:30:32 PST (-0800), Christoph Hellwig wrote: >> >> On Wed, Nov 29, 2017 at 05:55:19PM -0800, Olof Johansson wrote: >>> >>> In file included from ../lib/audit.c:8:0: >>>

Re: [patches] Re: [PATCH 08/10] RISC-V: Set __ARCH_WANT_RENAMEAT to pick up generic version

On Thu, Nov 30, 2017 at 10:38 AM, Palmer Dabbelt wrote: > On Thu, 30 Nov 2017 10:30:32 PST (-0800), Christoph Hellwig wrote: >> >> On Wed, Nov 29, 2017 at 05:55:19PM -0800, Olof Johansson wrote: >>> >>> In file included from ../lib/audit.c:8:0: >>> ../include/asm-generic/audit_dir_write.h:30:1:

[PATCH] sched/isolation: Make NO_HZ_FULL select CPU_ISOLATION

Commit 5c4991e24c69 ("sched/isolation: Split out new CONFIG_CPU_ISOLATION=y config from CONFIG_NO_HZ_FULL") can result in RCU CPU stall warnings when running rcutorture with CONFIG_NO_HZ_FULL_ALL=y and CONFIG_CPU_ISOLATION=n. These warnings are caused by RCU's grace-period kthreads sleeping for a

[PATCH] sched/isolation: Make NO_HZ_FULL select CPU_ISOLATION

Commit 5c4991e24c69 ("sched/isolation: Split out new CONFIG_CPU_ISOLATION=y config from CONFIG_NO_HZ_FULL") can result in RCU CPU stall warnings when running rcutorture with CONFIG_NO_HZ_FULL_ALL=y and CONFIG_CPU_ISOLATION=n. These warnings are caused by RCU's grace-period kthreads sleeping for a

Re: [PATCH v2 10/23] firmware: add helper to copy built-in data to pre-alloc buffer

On Wed, Nov 29, 2017 at 11:17:15AM +0100, Greg KH wrote: > On Mon, Nov 20, 2017 at 10:23:56AM -0800, Luis R. Rodriguez wrote: > > This makes it clearer that the parameters passed are only used for > > the preallocated buffer option, ie, when a caller uses: > > > > request_firmware_into_buf()

Re: [PATCH v2 10/23] firmware: add helper to copy built-in data to pre-alloc buffer

On Wed, Nov 29, 2017 at 11:17:15AM +0100, Greg KH wrote: > On Mon, Nov 20, 2017 at 10:23:56AM -0800, Luis R. Rodriguez wrote: > > This makes it clearer that the parameters passed are only used for > > the preallocated buffer option, ie, when a caller uses: > > > > request_firmware_into_buf()

[PATCH 1/8] ARM: dts: imx7d-sbc-iot: add initial iot gateway dts

From: Tyler Baker The Compulab IoT Gateway is based on an NXP i.MX7D, dual core Cortex-A7 clocking at 1GHz. It supports up to 2GB of DDR3, and 32GB of eMMC flash. Onboard, there are two gigabit ethernet controllers, 4 x USB2, RS485, and CAN. This platform is based

[PATCH 1/8] ARM: dts: imx7d-sbc-iot: add initial iot gateway dts

From: Tyler Baker The Compulab IoT Gateway is based on an NXP i.MX7D, dual core Cortex-A7 clocking at 1GHz. It supports up to 2GB of DDR3, and 32GB of eMMC flash. Onboard, there are two gigabit ethernet controllers, 4 x USB2, RS485, and CAN. This platform is based on the imx7d-cl-som-imx7

[PATCH 5/8] ARM: dts: imx7s: add node and supplies for vdd1p2

From: Tyler Baker Add the regulator nodes and supplies for vdd1p2. This regulator is used to power the GPC and USB HSIC PHY. Signed-off-by: Tyler Baker --- arch/arm/boot/dts/imx7s.dtsi | 17 - 1 file changed, 16

[PATCH 5/8] ARM: dts: imx7s: add node and supplies for vdd1p2

From: Tyler Baker Add the regulator nodes and supplies for vdd1p2. This regulator is used to power the GPC and USB HSIC PHY. Signed-off-by: Tyler Baker --- arch/arm/boot/dts/imx7s.dtsi | 17 - 1 file changed, 16 insertions(+), 1 deletion(-) diff --git

Re: [PATCH v7 1/5] add infrastructure for tagging functions as error injectable

On Wed, Nov 29, 2017 at 05:59:39PM +0100, Daniel Borkmann wrote: > On 11/28/2017 09:02 PM, Josef Bacik wrote: > > On Tue, Nov 28, 2017 at 11:58:41AM -0700, Jonathan Corbet wrote: > >> On Wed, 22 Nov 2017 16:23:30 -0500 > >> Josef Bacik wrote: > >>> From: Josef Bacik

[PATCH 2/8] ARM: dts: imx7: build imx7d-sbc-iot-imx7 dtb

From: Tyler Baker Build the imx7d-sbc-iot-imx7 device tree blob. Signed-off-by: Tyler Baker --- arch/arm/boot/dts/Makefile | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile

Re: [PATCH v7 1/5] add infrastructure for tagging functions as error injectable

On Wed, Nov 29, 2017 at 05:59:39PM +0100, Daniel Borkmann wrote: > On 11/28/2017 09:02 PM, Josef Bacik wrote: > > On Tue, Nov 28, 2017 at 11:58:41AM -0700, Jonathan Corbet wrote: > >> On Wed, 22 Nov 2017 16:23:30 -0500 > >> Josef Bacik wrote: > >>> From: Josef Bacik > >>> > >>> Using BPF we can

[PATCH 2/8] ARM: dts: imx7: build imx7d-sbc-iot-imx7 dtb

From: Tyler Baker Build the imx7d-sbc-iot-imx7 device tree blob. Signed-off-by: Tyler Baker --- arch/arm/boot/dts/Makefile | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile index d0381e9..0334137 100644 --- a/arch/arm/boot/dts/Makefile

[PATCH 4/8] ARM: dts: imx7s: add dma support

From: Tyler Baker Enable dma on all SPI and UART interfaces. Signed-off-by: Tyler Baker --- arch/arm/boot/dts/imx7s.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/imx7s.dtsi

[PATCH 4/8] ARM: dts: imx7s: add dma support

From: Tyler Baker Enable dma on all SPI and UART interfaces. Signed-off-by: Tyler Baker --- arch/arm/boot/dts/imx7s.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/imx7s.dtsi b/arch/arm/boot/dts/imx7s.dtsi index 82ad26e..7b85659 100644 ---

[PATCH 6/8] ARM: dts: imx7d-sbc-iot: enable PCIe peripheral

From: Tyler Baker Add a PCIe device tree node to enable PCIe support. Signed-off-by: Tyler Baker --- arch/arm/boot/dts/imx7d-sbc-iot-imx7.dts | 14 ++ 1 file changed, 14 insertions(+) diff --git

[PATCH 6/8] ARM: dts: imx7d-sbc-iot: enable PCIe peripheral

From: Tyler Baker Add a PCIe device tree node to enable PCIe support. Signed-off-by: Tyler Baker --- arch/arm/boot/dts/imx7d-sbc-iot-imx7.dts | 14 ++ 1 file changed, 14 insertions(+) diff --git a/arch/arm/boot/dts/imx7d-sbc-iot-imx7.dts

[PATCH 3/8] ARM: dts: imx7d-cl-som: add nodes for usbh, and usbotg2

From: Tyler Baker Add device tree nodes for the USB hub, and USB OTG. i2c2 on this platform supports low state retention power state so lets use it. Signed-off-by: Tyler Baker --- arch/arm/boot/dts/imx7d-cl-som-imx7.dts | 36

[PATCH 3/8] ARM: dts: imx7d-cl-som: add nodes for usbh, and usbotg2

From: Tyler Baker Add device tree nodes for the USB hub, and USB OTG. i2c2 on this platform supports low state retention power state so lets use it. Signed-off-by: Tyler Baker --- arch/arm/boot/dts/imx7d-cl-som-imx7.dts | 36 + 1 file changed, 28 insertions(+),

[PATCH 8/8] PCIe: imx6: imx7d: add support for phy refclk source

From: Tyler Baker In the i.MX7D the PCIe PHY can use either externel oscillator or internal PLL as a reference clock source. Add support for the PHY Reference Clock source including device tree property phy-ref-clk. External oscillator is used as a default

[PATCH 8/8] PCIe: imx6: imx7d: add support for phy refclk source

From: Tyler Baker In the i.MX7D the PCIe PHY can use either externel oscillator or internal PLL as a reference clock source. Add support for the PHY Reference Clock source including device tree property phy-ref-clk. External oscillator is used as a default reference clock source. Signed-off-by:

[PATCH v1] PCI: Remove PCI_REASSIGN_ALL_RSRC use on arm and arm64

From: Bjorn Helgaas On arm, PCI_REASSIGN_ALL_RSRC is used only in pcibios_assign_all_busses(), which helps decide whether to reconfigure bridge bus numbers. It has nothing to do with BAR assignments. On arm64 and powerpc, pcibios_assign_all_busses() tests

[PATCH v1] PCI: Remove PCI_REASSIGN_ALL_RSRC use on arm and arm64

From: Bjorn Helgaas On arm, PCI_REASSIGN_ALL_RSRC is used only in pcibios_assign_all_busses(), which helps decide whether to reconfigure bridge bus numbers. It has nothing to do with BAR assignments. On arm64 and powerpc, pcibios_assign_all_busses() tests PCI_REASSIGN_ALL_BUS, which makes more

[PATCH 0/8] ARM: dts: introduce Compulab IoT Gateway

From: Tyler Baker The Compulab IoT Gateway is based on an NXP i.MX7D, dual core Cortex-A7 clocking at 1GHz. It supports up to 2GB of DDR3, and 32GB of eMMC flash. Onboard, there are two gigabit ethernet controllers, 4 x USB2, RS485, and CAN. It uses the same SoM

[PATCH 0/8] ARM: dts: introduce Compulab IoT Gateway

From: Tyler Baker The Compulab IoT Gateway is based on an NXP i.MX7D, dual core Cortex-A7 clocking at 1GHz. It supports up to 2GB of DDR3, and 32GB of eMMC flash. Onboard, there are two gigabit ethernet controllers, 4 x USB2, RS485, and CAN. It uses the same SoM as the cl-som-imx7, but includes

[PATCH 7/8] ARM: dts: imx7s: add usb hsic phy domain

From: Tyler Baker The GPCv2 driver should control the MIPI, PCIe, and USB HSIC PHY regulators. Add the USB HSIC power domain to the GPC node. Signed-off-by: Tyler Baker --- arch/arm/boot/dts/imx7s.dtsi | 6 ++ 1 file changed, 6

[PATCH 7/8] ARM: dts: imx7s: add usb hsic phy domain

From: Tyler Baker The GPCv2 driver should control the MIPI, PCIe, and USB HSIC PHY regulators. Add the USB HSIC power domain to the GPC node. Signed-off-by: Tyler Baker --- arch/arm/boot/dts/imx7s.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/imx7s.dtsi

Re: [PATCH RFC 2/2] mm, hugetlb: do not rely on overcommit limit during migration

On Thu 30-11-17 20:57:43, Michal Hocko wrote: > On Thu 30-11-17 11:35:11, Mike Kravetz wrote: > > On 11/29/2017 11:57 PM, Michal Hocko wrote: > > > On Wed 29-11-17 11:52:53, Mike Kravetz wrote: > > >> On 11/29/2017 01:22 AM, Michal Hocko wrote: > > >>> What about this on top. I haven't tested this

Re: [PATCH RFC 2/2] mm, hugetlb: do not rely on overcommit limit during migration

On Thu 30-11-17 20:57:43, Michal Hocko wrote: > On Thu 30-11-17 11:35:11, Mike Kravetz wrote: > > On 11/29/2017 11:57 PM, Michal Hocko wrote: > > > On Wed 29-11-17 11:52:53, Mike Kravetz wrote: > > >> On 11/29/2017 01:22 AM, Michal Hocko wrote: > > >>> What about this on top. I haven't tested this

Re: [PATCH 0/5] PCI: Add support to the Cadence PCIe controller

Le 30/11/2017 à 19:45, Cyrille Pitchen a écrit : > Hi all, > > Le 30/11/2017 à 19:18, Lorenzo Pieralisi a écrit : >> On Thu, Nov 30, 2017 at 12:43:20PM +0530, Kishon Vijay Abraham I wrote: >> >> [...] >> > For linux-next, I applied this series on top of Kishon's patch > ("PCI: endpoint:

Re: [PATCH 0/5] PCI: Add support to the Cadence PCIe controller

Le 30/11/2017 à 19:45, Cyrille Pitchen a écrit : > Hi all, > > Le 30/11/2017 à 19:18, Lorenzo Pieralisi a écrit : >> On Thu, Nov 30, 2017 at 12:43:20PM +0530, Kishon Vijay Abraham I wrote: >> >> [...] >> > For linux-next, I applied this series on top of Kishon's patch > ("PCI: endpoint:

[PATCH] drm/nouveau/mmu: fix odd_ptr_err.cocci warnings

The kbuild test bot complained about a new coccinelle warning nearby, which sparked a discussion about the assignment to 'memory' inside of the conditional expression. See Link below for the original post. Fix the assignment to silence the coccinelle warning and also make the code look a little

[PATCH] drm/nouveau/mmu: fix odd_ptr_err.cocci warnings

The kbuild test bot complained about a new coccinelle warning nearby, which sparked a discussion about the assignment to 'memory' inside of the conditional expression. See Link below for the original post. Fix the assignment to silence the coccinelle warning and also make the code look a little

Re: [PATCH 15/24] x86/mm: Allow flushing for future ASID switches

On Thu, Nov 30, 2017 at 10:48:56AM -0800, Andy Lutomirski wrote: > Should it be > tlb_flush_shared_nonglobals_if_kernel_and_user_pagetables_are_separate()? Its effectively invpcid_flush_all_other() or something like that. Of course, its not invpcid based, so we should not name it such.

Re: [PATCH 15/24] x86/mm: Allow flushing for future ASID switches

On Thu, Nov 30, 2017 at 10:48:56AM -0800, Andy Lutomirski wrote: > Should it be > tlb_flush_shared_nonglobals_if_kernel_and_user_pagetables_are_separate()? Its effectively invpcid_flush_all_other() or something like that. Of course, its not invpcid based, so we should not name it such.

Re: [PATCH v3 5/6] ARM: ep93xx: ts72xx: cosmetic: Add some description to ts72xx code

Hello Hartley! On Thu, 30 Nov 2017 17:23:02 + Hartley Sweeten wrote: > > +/** > > +*** > > + * IO map > > + > > +*** > >

Re: [PATCH v3 5/6] ARM: ep93xx: ts72xx: cosmetic: Add some description to ts72xx code

Hello Hartley! On Thu, 30 Nov 2017 17:23:02 + Hartley Sweeten wrote: > > +/** > > +*** > > + * IO map > > + > > +*** > > +**/ > > There is also something

Re: [PATCH 1/2] x86/stacktrace: do not fail when regs on stack for ORC

On Thu, Nov 30, 2017 at 01:57:10PM -0600, Josh Poimboeuf wrote: > On Thu, Nov 30, 2017 at 09:03:24AM +0100, Jiri Slaby wrote: > > save_stack_trace_reliable now returns "non reliable" when there are > > kernel pt_regs on stack. This means an interrupt or exception happened. > > Somewhere down the

Re: [PATCH 1/2] x86/stacktrace: do not fail when regs on stack for ORC

On Thu, Nov 30, 2017 at 01:57:10PM -0600, Josh Poimboeuf wrote: > On Thu, Nov 30, 2017 at 09:03:24AM +0100, Jiri Slaby wrote: > > save_stack_trace_reliable now returns "non reliable" when there are > > kernel pt_regs on stack. This means an interrupt or exception happened. > > Somewhere down the

Re: [pcpu] BUG: KASAN: use-after-scope in pcpu_setup_first_chunk+0x1e3b/0x29e2

On 30 November 2017 at 19:56, Kees Cook wrote: > On Thu, Nov 30, 2017 at 11:22 AM, Dennis Zhou wrote: >> Hi Dmitry and Kees, >> >> On Thu, Nov 30, 2017 at 10:10:41AM -0800, Kees Cook wrote: >>> > Are we sure that structleak plugin is not at fault? If

Re: [pcpu] BUG: KASAN: use-after-scope in pcpu_setup_first_chunk+0x1e3b/0x29e2

On 30 November 2017 at 19:56, Kees Cook wrote: > On Thu, Nov 30, 2017 at 11:22 AM, Dennis Zhou wrote: >> Hi Dmitry and Kees, >> >> On Thu, Nov 30, 2017 at 10:10:41AM -0800, Kees Cook wrote: >>> > Are we sure that structleak plugin is not at fault? If yes, then we >>> > need to report this to

Re: [PATCH RFC 2/2] mm, hugetlb: do not rely on overcommit limit during migration

On Thu 30-11-17 11:35:11, Mike Kravetz wrote: > On 11/29/2017 11:57 PM, Michal Hocko wrote: > > On Wed 29-11-17 11:52:53, Mike Kravetz wrote: > >> On 11/29/2017 01:22 AM, Michal Hocko wrote: > >>> What about this on top. I haven't tested this yet though. > >> > >> Yes, this would work. > >> > >>

Re: [PATCH RFC 2/2] mm, hugetlb: do not rely on overcommit limit during migration

On Thu 30-11-17 11:35:11, Mike Kravetz wrote: > On 11/29/2017 11:57 PM, Michal Hocko wrote: > > On Wed 29-11-17 11:52:53, Mike Kravetz wrote: > >> On 11/29/2017 01:22 AM, Michal Hocko wrote: > >>> What about this on top. I haven't tested this yet though. > >> > >> Yes, this would work. > >> > >>

Re: [PATCH v2 01/18] dt-bindings: panel: lvds: Document power-supply property

On Thu, Nov 30, 2017 at 9:30 AM, Maxime Ripard wrote: > Hi Rob, > > On Tue, Nov 28, 2017 at 11:48:47AM -0600, Rob Herring wrote: >> Please CC DT list. >> >> On Mon, Nov 27, 2017 at 9:41 AM, Maxime Ripard >> wrote: >> > The

Re: [PATCH v2 01/18] dt-bindings: panel: lvds: Document power-supply property

On Thu, Nov 30, 2017 at 9:30 AM, Maxime Ripard wrote: > Hi Rob, > > On Tue, Nov 28, 2017 at 11:48:47AM -0600, Rob Herring wrote: >> Please CC DT list. >> >> On Mon, Nov 27, 2017 at 9:41 AM, Maxime Ripard >> wrote: >> > The power-supply property is used by a vast majority of panels, including >>

Re: [PATCH 1/2] x86/stacktrace: do not fail when regs on stack for ORC

On Thu, Nov 30, 2017 at 09:03:24AM +0100, Jiri Slaby wrote: > save_stack_trace_reliable now returns "non reliable" when there are > kernel pt_regs on stack. This means an interrupt or exception happened. > Somewhere down the route. It is a problem for frame pointer unwinder, > because the frame

Re: [PATCH 1/2] x86/stacktrace: do not fail when regs on stack for ORC

On Thu, Nov 30, 2017 at 09:03:24AM +0100, Jiri Slaby wrote: > save_stack_trace_reliable now returns "non reliable" when there are > kernel pt_regs on stack. This means an interrupt or exception happened. > Somewhere down the route. It is a problem for frame pointer unwinder, > because the frame

Re: [RFC] Rebasing the IDR

Adding dri-devel, I think a pile of those are in drm. On Thu, Nov 30, 2017 at 6:36 PM, Matthew Wilcox wrote: > About 40 of the approximately 180 users of the IDR in the kernel are > "1-based" instead of "0-based". That is, they never want to have ID 0 > allocated; they want

Re: [RFC] Rebasing the IDR

Adding dri-devel, I think a pile of those are in drm. On Thu, Nov 30, 2017 at 6:36 PM, Matthew Wilcox wrote: > About 40 of the approximately 180 users of the IDR in the kernel are > "1-based" instead of "0-based". That is, they never want to have ID 0 > allocated; they want to see IDs allocated

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