[GIT PULL][PATCH 2/2] ktest: Make sure wait_for_input does honor the timeout

From: "Steven Rostedt (VMware)" The function wait_for_input takes in a timeout, and even has a default timeout. But if for some reason the STDIN descriptor keeps sending in data, the function will never time out. The timout is to wait for the data from the passed in file

[GIT PULL][PATCH 2/2] ktest: Make sure wait_for_input does honor the timeout

From: "Steven Rostedt (VMware)" The function wait_for_input takes in a timeout, and even has a default timeout. But if for some reason the STDIN descriptor keeps sending in data, the function will never time out. The timout is to wait for the data from the passed in file descriptor, not for

Re: [v6 PATCH 19/21] x86/traps: Fixup general protection faults caused by UMIP

On Tue, Mar 7, 2017 at 4:32 PM, Ricardo Neri wrote: > If the User-Mode Instruction Prevention CPU feature is available and > enabled, a general protection fault will be issued if the instructions > sgdt, sldt, sidt, str or smsw are executed from user-mode

Re: [v6 PATCH 19/21] x86/traps: Fixup general protection faults caused by UMIP

On Tue, Mar 7, 2017 at 4:32 PM, Ricardo Neri wrote: > If the User-Mode Instruction Prevention CPU feature is available and > enabled, a general protection fault will be issued if the instructions > sgdt, sldt, sidt, str or smsw are executed from user-mode context > (CPL > 0). If the fault was

Re: [PATCH 0/7] 5-level paging: prepare generic code

On Wed 08-03-17 18:07:42, Kirill A. Shutemov wrote: > On Wed, Mar 08, 2017 at 03:25:01PM +0100, Michal Hocko wrote: > > Btw. my build test machinery has reported this: > > microblaze/allnoconfig > > Thanks. > > Fixup is below. I guess it should be folded into 4/7. yes, this has passed the

Re: [PATCH 0/7] 5-level paging: prepare generic code

On Wed 08-03-17 18:07:42, Kirill A. Shutemov wrote: > On Wed, Mar 08, 2017 at 03:25:01PM +0100, Michal Hocko wrote: > > Btw. my build test machinery has reported this: > > microblaze/allnoconfig > > Thanks. > > Fixup is below. I guess it should be folded into 4/7. yes, this has passed the

[PATCH] tun: remove copyright printing

Printing copyright does not give any useful information on the boot process. Furthermore, the email address printed is obsolete since commit ba57b6f20429 ("MAINTAINERS: fix bouncing tun/tap entries") Signed-off-by: Corentin Labbe --- drivers/net/tun.c | 1 - 1 file

[PATCH] tun: remove copyright printing

Printing copyright does not give any useful information on the boot process. Furthermore, the email address printed is obsolete since commit ba57b6f20429 ("MAINTAINERS: fix bouncing tun/tap entries") Signed-off-by: Corentin Labbe --- drivers/net/tun.c | 1 - 1 file changed, 1 deletion(-) diff

Re: [PATCH 3/5] fs, xfs: convert xlog_ticket.t_ref from atomic_t to refcount_t

> - ASSERT(atomic_read(>t_ref) > 0); > - atomic_inc(>t_ref); > + ASSERT(refcount_read(>t_ref) > 0); > + refcount_inc(>t_ref); With strict refcount semantics refcount_inc should check that the count is larger than 0, otherwise we'd need to use recount_inc_not_zero or whatever

Re: [PATCH 3/5] fs, xfs: convert xlog_ticket.t_ref from atomic_t to refcount_t

> - ASSERT(atomic_read(>t_ref) > 0); > - atomic_inc(>t_ref); > + ASSERT(refcount_read(>t_ref) > 0); > + refcount_inc(>t_ref); With strict refcount semantics refcount_inc should check that the count is larger than 0, otherwise we'd need to use recount_inc_not_zero or whatever

Re: [PATCH] mux-core: make it explicitly non-modular

On 2017-03-08 15:38, Paul Gortmaker wrote: > [Re: [PATCH] mux-core: make it explicitly non-modular] On 08/03/2017 (Wed > 10:38) Peter Rosin wrote: > >> On 2017-03-07 23:41, Paul Gortmaker wrote: >>> The Kconfig currently controlling compilation of this code is: >>> >>>

Re: [PATCH] mux-core: make it explicitly non-modular

On 2017-03-08 15:38, Paul Gortmaker wrote: > [Re: [PATCH] mux-core: make it explicitly non-modular] On 08/03/2017 (Wed > 10:38) Peter Rosin wrote: > >> On 2017-03-07 23:41, Paul Gortmaker wrote: >>> The Kconfig currently controlling compilation of this code is: >>> >>>

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

On Wed, Mar 08, 2017 at 04:45:58PM +0100, Dmitry Vyukov wrote: > On Wed, Mar 8, 2017 at 4:43 PM, Mark Rutland wrote: > > On Wed, Mar 08, 2017 at 04:27:11PM +0100, Dmitry Vyukov wrote: > >> On Wed, Mar 8, 2017 at 4:20 PM, Mark Rutland wrote: > >> > As

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

On Wed, Mar 08, 2017 at 04:45:58PM +0100, Dmitry Vyukov wrote: > On Wed, Mar 8, 2017 at 4:43 PM, Mark Rutland wrote: > > On Wed, Mar 08, 2017 at 04:27:11PM +0100, Dmitry Vyukov wrote: > >> On Wed, Mar 8, 2017 at 4:20 PM, Mark Rutland wrote: > >> > As in my other reply, I'd prefer that we wrapped

Re: [PATCH 0/2] usb: gadget: f_uvc: SuperSpeed fixes

Hi Roger, Thank you for the patches. On Wednesday 08 Mar 2017 16:05:42 Roger Quadros wrote: > Hi Laurent & Felipe, > > These are some fixes for SuperSpeed case. For both patches, Reviewed-by: Laurent Pinchart > -- > cheers, > -roger > > Roger Quadros (2):

Re: [PATCH 0/2] usb: gadget: f_uvc: SuperSpeed fixes

Hi Roger, Thank you for the patches. On Wednesday 08 Mar 2017 16:05:42 Roger Quadros wrote: > Hi Laurent & Felipe, > > These are some fixes for SuperSpeed case. For both patches, Reviewed-by: Laurent Pinchart > -- > cheers, > -roger > > Roger Quadros (2): > usb: gadget: f_uvc: Fix

Re: [PATCH v2 1/2] doc: bindings: Add bindings documentation for mtd nvmem

On Tue, 7 Mar 2017 22:01:07 +0100 Boris Brezillon wrote: > On Tue, 7 Mar 2017 09:26:03 +0100 > Alban wrote: > > > Config data for drivers, like MAC addresses, is often stored in MTD. > > Add a binding that define how such data storage can be

Re: [PATCH v2 1/2] doc: bindings: Add bindings documentation for mtd nvmem

On Tue, 7 Mar 2017 22:01:07 +0100 Boris Brezillon wrote: > On Tue, 7 Mar 2017 09:26:03 +0100 > Alban wrote: > > > Config data for drivers, like MAC addresses, is often stored in MTD. > > Add a binding that define how such data storage can be represented in > > device tree. > > > >

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

On Wed, Mar 8, 2017 at 4:43 PM, Mark Rutland wrote: > On Wed, Mar 08, 2017 at 04:27:11PM +0100, Dmitry Vyukov wrote: >> On Wed, Mar 8, 2017 at 4:20 PM, Mark Rutland wrote: >> > As in my other reply, I'd prefer that we wrapped the (arch-specific) >> >

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

On Wed, Mar 8, 2017 at 4:43 PM, Mark Rutland wrote: > On Wed, Mar 08, 2017 at 04:27:11PM +0100, Dmitry Vyukov wrote: >> On Wed, Mar 8, 2017 at 4:20 PM, Mark Rutland wrote: >> > As in my other reply, I'd prefer that we wrapped the (arch-specific) >> > atomic implementations such that we can

Re: [PATCH 1/2] reset: add reset-simple to unify socfpga, stm32, and sunxi

Hi, On 08/03/17 12:20, Philipp Zabel wrote: > On Wed, 2017-03-08 at 12:05 +0100, Alexandre Torgue wrote: >> Hi Philipp, >> >> On 03/08/2017 11:19 AM, Andre Przywara wrote: >>> Hi, >>> >>> On 08/03/17 09:54, Philipp Zabel wrote: Reset operations for simple reset controllers with reset lines

Re: [PATCH 1/2] reset: add reset-simple to unify socfpga, stm32, and sunxi

Hi, On 08/03/17 12:20, Philipp Zabel wrote: > On Wed, 2017-03-08 at 12:05 +0100, Alexandre Torgue wrote: >> Hi Philipp, >> >> On 03/08/2017 11:19 AM, Andre Przywara wrote: >>> Hi, >>> >>> On 08/03/17 09:54, Philipp Zabel wrote: Reset operations for simple reset controllers with reset lines

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

On Wed, Mar 08, 2017 at 04:27:11PM +0100, Dmitry Vyukov wrote: > On Wed, Mar 8, 2017 at 4:20 PM, Mark Rutland wrote: > > As in my other reply, I'd prefer that we wrapped the (arch-specific) > > atomic implementations such that we can instrument them explicitly in a > > core

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

On Wed, Mar 08, 2017 at 04:27:11PM +0100, Dmitry Vyukov wrote: > On Wed, Mar 8, 2017 at 4:20 PM, Mark Rutland wrote: > > As in my other reply, I'd prefer that we wrapped the (arch-specific) > > atomic implementations such that we can instrument them explicitly in a > > core header. That means

Re: [PATCH v2 2/2] Staging: comedi: comedi_fops: Fix "out of minor numbers for board device files"

On 07/03/17 18:13, Cheah Kok Cheong wrote: If comedi module is loaded with the following max allowed parameter [comedi_num_legacy_minors=48], subsequent loading of an auto-configured device will fail at auto-configuration. If there's no fall back in place then module loading will fail. In this

Re: [PATCH v2 2/2] Staging: comedi: comedi_fops: Fix "out of minor numbers for board device files"

On 07/03/17 18:13, Cheah Kok Cheong wrote: If comedi module is loaded with the following max allowed parameter [comedi_num_legacy_minors=48], subsequent loading of an auto-configured device will fail at auto-configuration. If there's no fall back in place then module loading will fail. In this

Re: [PATCH 20/26] IB/ocrdma: Delete an unnecessary variable assignment in ocrdma_alloc_mr()

Acked-By: Devesh Sharma On Wed, Mar 8, 2017 at 6:52 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 8 Mar 2017 10:00:41 +0100 > > Delete an assignment for the local variable "status" in

Re: [PATCH 20/26] IB/ocrdma: Delete an unnecessary variable assignment in ocrdma_alloc_mr()

Acked-By: Devesh Sharma On Wed, Mar 8, 2017 at 6:52 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 8 Mar 2017 10:00:41 +0100 > > Delete an assignment for the local variable "status" in an if branch > because the desired failure indication is already specified by a constant >

Re: [PATCH 3/6] mm/migrate: Add copy_pages_mthread function

On 02/17/2017 05:57 PM, kbuild test robot wrote: > Hi Zi, > > [auto build test WARNING on linus/master] > [also build test WARNING on v4.10-rc8 next-20170216] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: >

Re: [PATCH 3/6] mm/migrate: Add copy_pages_mthread function

On 02/17/2017 05:57 PM, kbuild test robot wrote: > Hi Zi, > > [auto build test WARNING on linus/master] > [also build test WARNING on v4.10-rc8 next-20170216] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: >

Re: [PATCH 2/2] x86/mm/KASLR: Correct the upper boundary of KALSR mm regions if adjacent to EFI

Thanks for the change. Acked-by: Thomas Garnier On Wed, Mar 8, 2017 at 12:35 AM, Bhupesh Sharma wrote: > On Wed, Mar 8, 2017 at 1:48 PM, Dave Young wrote: >> On 03/08/17 at 03:47pm, Baoquan He wrote: >>> EFI allocates runtime

Re: [PATCH 2/2] x86/mm/KASLR: Correct the upper boundary of KALSR mm regions if adjacent to EFI

Thanks for the change. Acked-by: Thomas Garnier On Wed, Mar 8, 2017 at 12:35 AM, Bhupesh Sharma wrote: > On Wed, Mar 8, 2017 at 1:48 PM, Dave Young wrote: >> On 03/08/17 at 03:47pm, Baoquan He wrote: >>> EFI allocates runtime services regions top-down, starting from EFI_VA_START >>> to

Re: [PATCH 6/6] sysctl: Add global tunable mt_page_copy

On 02/17/2017 09:00 PM, kbuild test robot wrote: > Hi Zi, > > [auto build test ERROR on linus/master] > [also build test ERROR on v4.10-rc8 next-20170217] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: >

Re: [PATCH 6/6] sysctl: Add global tunable mt_page_copy

On 02/17/2017 09:00 PM, kbuild test robot wrote: > Hi Zi, > > [auto build test ERROR on linus/master] > [also build test ERROR on v4.10-rc8 next-20170217] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: >

Re: [f2fs-dev] [PATCH] f2fs: don't allow rename unencrypted file to encrypted directory

On 3/8/2017 20:08, Chao Yu wrote: > In commit d9cdc9033181 ("ext4 crypto: enforce context consistency") we > declared that: > > 2) All files or directories in a directory must be protected using the > same key as their containing directory. > > But in f2fs_cross_rename there is a

[PATCH v3 2/3] Input: synaptics - allocate a Synaptics Intertouch device

Most of the Synaptics devices are connected through PS/2 and a different bus (SMBus or HID over I2C). The secondary bus capability is indicated by the InterTouch bit in extended capability 0x0C. When we encounter such a device, we can create a platform device with the information gathered through

[PATCH v3 2/3] Input: synaptics - allocate a Synaptics Intertouch device

Most of the Synaptics devices are connected through PS/2 and a different bus (SMBus or HID over I2C). The secondary bus capability is indicated by the InterTouch bit in extended capability 0x0C. When we encounter such a device, we can create a platform device with the information gathered through

Re: [f2fs-dev] [PATCH] f2fs: don't allow rename unencrypted file to encrypted directory

On 3/8/2017 20:08, Chao Yu wrote: > In commit d9cdc9033181 ("ext4 crypto: enforce context consistency") we > declared that: > > 2) All files or directories in a directory must be protected using the > same key as their containing directory. > > But in f2fs_cross_rename there is a

Re: [PATCH] iommu/arm-smmu: Report smmu type in dmesg

On 03/06/2017 02:58 PM, Robert Richter wrote: The ARM SMMU detection especially depends from system firmware. For better diagnostic, log the detected type in dmesg. The smmu type's name is now stored in struct arm_smmu_type and ACPI code is modified to use that struct too. Rename

Re: [PATCH] iommu/arm-smmu: Report smmu type in dmesg

On 03/06/2017 02:58 PM, Robert Richter wrote: The ARM SMMU detection especially depends from system firmware. For better diagnostic, log the detected type in dmesg. The smmu type's name is now stored in struct arm_smmu_type and ACPI code is modified to use that struct too. Rename

Re: [PATCH 18/26] IB/ocrdma: Use kcalloc() in three functions

Acked-By:Devesh Sharma On Wed, Mar 8, 2017 at 6:49 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 8 Mar 2017 09:19:47 +0100 > > * Multiplications for the size determination of memory

Re: [PATCH 18/26] IB/ocrdma: Use kcalloc() in three functions

Acked-By:Devesh Sharma On Wed, Mar 8, 2017 at 6:49 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 8 Mar 2017 09:19:47 +0100 > > * Multiplications for the size determination of memory allocations > indicated that array data structures should be processed. > Thus reuse the

Re: [PATCH] futex: move debug_rt_mutex_free_waiter() further down

On 2017-03-08 16:29:02 [+0100], To Peter Zijlstra wrote: > Without this, futex_requeue_pi_signal_restart will trigger > > |kernel BUG at locking/rtmutex_common.h:55! > |Call Trace: > | rt_mutex_cleanup_proxy_lock+0x54/0x90 > | futex_wait_requeue_pi.constprop.21+0x387/0x4d0 > |

Re: [PATCH] futex: move debug_rt_mutex_free_waiter() further down

On 2017-03-08 16:29:02 [+0100], To Peter Zijlstra wrote: > Without this, futex_requeue_pi_signal_restart will trigger > > |kernel BUG at locking/rtmutex_common.h:55! > |Call Trace: > | rt_mutex_cleanup_proxy_lock+0x54/0x90 > | futex_wait_requeue_pi.constprop.21+0x387/0x4d0 > |

Re: [RFC,v2 3/3] sched: ignore task_h_load for CPU_NEWLY_IDLE

Hello. Let's decide how to proceed with https://lkml.org/lkml/2017/2/14/334 patch. Despite it is not a big change, i think it is important and ready to be submited, unless there are still any comments. -- Uladzislau Rezki On Thu, Feb 16, 2017 at 12:20 PM, Uladzislau Rezki

Re: [RFC,v2 3/3] sched: ignore task_h_load for CPU_NEWLY_IDLE

Hello. Let's decide how to proceed with https://lkml.org/lkml/2017/2/14/334 patch. Despite it is not a big change, i think it is important and ready to be submited, unless there are still any comments. -- Uladzislau Rezki On Thu, Feb 16, 2017 at 12:20 PM, Uladzislau Rezki wrote: > On Wed, Feb

[PATCH] futex: move debug_rt_mutex_free_waiter() further down

Without this, futex_requeue_pi_signal_restart will trigger |kernel BUG at locking/rtmutex_common.h:55! |Call Trace: | rt_mutex_cleanup_proxy_lock+0x54/0x90 | futex_wait_requeue_pi.constprop.21+0x387/0x4d0 | do_futex+0x289/0xbf0 |RIP: remove_waiter+0x157/0x170 RSP: c9e0fbe0 with BUG

Re: [PATCH 26/26] IB/ocrdma: Adjust further ten checks for null pointers

Acked-By: Devesh Sharma On Wed, Mar 8, 2017 at 7:04 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 8 Mar 2017 12:50:14 +0100 > MIME-Version: 1.0 > Content-Type: text/plain; charset=UTF-8

[PATCH] futex: move debug_rt_mutex_free_waiter() further down

Without this, futex_requeue_pi_signal_restart will trigger |kernel BUG at locking/rtmutex_common.h:55! |Call Trace: | rt_mutex_cleanup_proxy_lock+0x54/0x90 | futex_wait_requeue_pi.constprop.21+0x387/0x4d0 | do_futex+0x289/0xbf0 |RIP: remove_waiter+0x157/0x170 RSP: c9e0fbe0 with BUG

Re: [PATCH 26/26] IB/ocrdma: Adjust further ten checks for null pointers

Acked-By: Devesh Sharma On Wed, Mar 8, 2017 at 7:04 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 8 Mar 2017 12:50:14 +0100 > MIME-Version: 1.0 > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: 8bit > > The script “checkpatch.pl“ pointed information out

Re: [PATCH 15/26] IB/ocrdma: Delete an error message for a failed memory allocation in ocrdma_add()

On Wed, Mar 08, 2017 at 02:13:11PM +0100, SF Markus Elfring wrote: > From: Markus Elfring > Date: Tue, 7 Mar 2017 22:23:17 +0100 > > Omit an extra message for a memory allocation failure in this function. > > Link: >

Re: [PATCH 15/26] IB/ocrdma: Delete an error message for a failed memory allocation in ocrdma_add()

On Wed, Mar 08, 2017 at 02:13:11PM +0100, SF Markus Elfring wrote: > From: Markus Elfring > Date: Tue, 7 Mar 2017 22:23:17 +0100 > > Omit an extra message for a memory allocation failure in this function. > > Link: >

Re: [PATCH v2 1/2] net: sched: make default fifo qdiscs appear in the dump

On Wed, 8 Mar 2017, Eric Dumazet wrote: > > +++ b/net/sched/sch_qfq.c > > @@ -494,6 +494,8 @@ static int qfq_change_class(struct Qdisc *sch, u32 > > classid, u32 parentid, > > goto destroy_class; > > } > > > > + if (cl->qdisc != _qdisc) > > +

Re: [PATCH v2 1/2] net: sched: make default fifo qdiscs appear in the dump

On Wed, 8 Mar 2017, Eric Dumazet wrote: > > +++ b/net/sched/sch_qfq.c > > @@ -494,6 +494,8 @@ static int qfq_change_class(struct Qdisc *sch, u32 > > classid, u32 parentid, > > goto destroy_class; > > } > > > > + if (cl->qdisc != _qdisc) > > +

Re: [PATCH v2 05/21] x86/xen: split off enlighten_hvm.c

On 02/03/17 18:53, Vitaly Kuznetsov wrote: > Move PVHVM related code to enlighten_hvm.c. Three functions: > xen_cpuhp_setup(), xen_reboot(), xen_emergency_restart() are shared, drop > static qualifier from them. These functions will go to common code once > it is split from enlighten.c. > >

[PATCH 16/26] IB/ocrdma: Adjust a null pointer check in ocrdma_alloc_resources()

From: Markus Elfring Date: Tue, 7 Mar 2017 22:34:33 +0100 The script "checkpatch.pl" pointed information out like the following. Comparison to NULL could be written "!dev->stag_arr". Thus fix the affected source code place. Signed-off-by: Markus Elfring

Re: [PATCH v2 05/21] x86/xen: split off enlighten_hvm.c

On 02/03/17 18:53, Vitaly Kuznetsov wrote: > Move PVHVM related code to enlighten_hvm.c. Three functions: > xen_cpuhp_setup(), xen_reboot(), xen_emergency_restart() are shared, drop > static qualifier from them. These functions will go to common code once > it is split from enlighten.c. > >

[PATCH 16/26] IB/ocrdma: Adjust a null pointer check in ocrdma_alloc_resources()

From: Markus Elfring Date: Tue, 7 Mar 2017 22:34:33 +0100 The script "checkpatch.pl" pointed information out like the following. Comparison to NULL could be written "!dev->stag_arr". Thus fix the affected source code place. Signed-off-by: Markus Elfring ---

Re: [PATCH v2 08/22] PCI: dwc: designware: Add EP mode support

Às 1:31 PM de 3/8/2017, Kishon Vijay Abraham I escreveu: > Hi, > > On Wednesday 08 March 2017 05:07 PM, Joao Pinto wrote: >> Às 11:35 AM de 3/8/2017, Kishon Vijay Abraham I escreveu: >>> Hi, >>> >>> On Wednesday 08 March 2017 05:02 PM, Joao Pinto wrote: Hi Kishon, >> Can you

Re: [PATCH v2 08/22] PCI: dwc: designware: Add EP mode support

Às 1:31 PM de 3/8/2017, Kishon Vijay Abraham I escreveu: > Hi, > > On Wednesday 08 March 2017 05:07 PM, Joao Pinto wrote: >> Às 11:35 AM de 3/8/2017, Kishon Vijay Abraham I escreveu: >>> Hi, >>> >>> On Wednesday 08 March 2017 05:02 PM, Joao Pinto wrote: Hi Kishon, >> Can you

Re: [PATCH v2 08/22] PCI: dwc: designware: Add EP mode support

Às 3:32 PM de 3/8/2017, Joao Pinto escreveu: > Às 1:31 PM de 3/8/2017, Kishon Vijay Abraham I escreveu: >> Hi, >> >> On Wednesday 08 March 2017 05:07 PM, Joao Pinto wrote: >>> Às 11:35 AM de 3/8/2017, Kishon Vijay Abraham I escreveu: Hi, On Wednesday 08 March 2017 05:02 PM, Joao

Re: [PATCH v2 08/22] PCI: dwc: designware: Add EP mode support

Às 3:32 PM de 3/8/2017, Joao Pinto escreveu: > Às 1:31 PM de 3/8/2017, Kishon Vijay Abraham I escreveu: >> Hi, >> >> On Wednesday 08 March 2017 05:07 PM, Joao Pinto wrote: >>> Às 11:35 AM de 3/8/2017, Kishon Vijay Abraham I escreveu: Hi, On Wednesday 08 March 2017 05:02 PM, Joao

RFC: SysRq nice-all-RT-tasks is broken

Hi, It appears that triggering the SysRq nice-all-RT-tasks from the console while a real task is active is leading to panic the system like this : sysrq: SysRq : Nice All RT Tasks [ cut here ] kernel BUG at /build/linux-twbIHf/linux-4.10.0/kernel/sched/core.c:4089!

RFC: SysRq nice-all-RT-tasks is broken

Hi, It appears that triggering the SysRq nice-all-RT-tasks from the console while a real task is active is leading to panic the system like this : sysrq: SysRq : Nice All RT Tasks [ cut here ] kernel BUG at /build/linux-twbIHf/linux-4.10.0/kernel/sched/core.c:4089!

[PATCH v3 1/3] input: serio - allow others to specify a driver for a serio device

The Lenovo Thinkpads use RMI4 over SMBus in addition to PS/2 for their trackpad. The problem is that the device doesn't enumerate itself besides some registers in PS/2. Once the initial PS/2 initialization has been made, we need a way to unbind psmouse from the touchpad and use a different

[PATCH v3 1/3] input: serio - allow others to specify a driver for a serio device

The Lenovo Thinkpads use RMI4 over SMBus in addition to PS/2 for their trackpad. The problem is that the device doesn't enumerate itself besides some registers in PS/2. Once the initial PS/2 initialization has been made, we need a way to unbind psmouse from the touchpad and use a different

Re: [PATCH 0/2] ARM: dts: socfpga: Add support for PMU on Arria5/Cyclone5

On 02/28/2017 09:52 AM, Florian Vaussard wrote: > Hi, > > These patches add suport for ARM Performance Monitor Units on Arria5 and > Cyclone5 SoCFPGA. This was tested on a Cyclone 5 SoC DK board. > > Side note: the same change can be probably applied to Arria10 as well, > but we do not have

Re: [PATCH 0/2] ARM: dts: socfpga: Add support for PMU on Arria5/Cyclone5

On 02/28/2017 09:52 AM, Florian Vaussard wrote: > Hi, > > These patches add suport for ARM Performance Monitor Units on Arria5 and > Cyclone5 SoCFPGA. This was tested on a Cyclone 5 SoC DK board. > > Side note: the same change can be probably applied to Arria10 as well, > but we do not have

Re: [PATCH 21/26] IB/ocrdma: Improve another size determination in ocrdma_create_srq()

Acked-By: Devesh Sharma On Wed, Mar 8, 2017 at 6:54 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 8 Mar 2017 10:10:50 +0100 > > Replace the specification of a data type by a pointer

Applied "ASoC: fsl: Remove unneeded init of static variable" to the asoc tree

The patch ASoC: fsl: Remove unneeded init of static variable has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Re: [PATCH 21/26] IB/ocrdma: Improve another size determination in ocrdma_create_srq()

Acked-By: Devesh Sharma On Wed, Mar 8, 2017 at 6:54 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 8 Mar 2017 10:10:50 +0100 > > Replace the specification of a data type by a pointer dereference > as the parameter for the operator "sizeof" to make the corresponding size >

Applied "ASoC: fsl: Remove unneeded init of static variable" to the asoc tree

The patch ASoC: fsl: Remove unneeded init of static variable has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

[PATCH v3 3/3] Input: add a PS/2 to SMBus platform module

This driver is a glue between PS/2 devices that enumerate the RMI4 devices and Elan touchpads to the RMI4 (or Elan) SMBus driver. We use an intermediate platform device to not add a dependency between psmouse and I2C. It also handles the subtleties of going around the serio mutex lock by

[PATCH v3 3/3] Input: add a PS/2 to SMBus platform module

This driver is a glue between PS/2 devices that enumerate the RMI4 devices and Elan touchpads to the RMI4 (or Elan) SMBus driver. We use an intermediate platform device to not add a dependency between psmouse and I2C. It also handles the subtleties of going around the serio mutex lock by

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

Hi, On Wed, Mar 08, 2017 at 02:42:10PM +0100, Dmitry Vyukov wrote: > I think if we scope compiler atomic builtins to KASAN/KTSAN/KMSAN (and > consequently x86/arm64) initially, it becomes more realistic. For the > tools we don't care about absolute efficiency and this gets rid of > Will's points

Re: [PATCH] f2fs: allocate a bio for discarding when actually issuing it

On Tue, Mar 07, 2017 at 06:33:33PM -0800, Jaegeuk Kim wrote: > Let's allocate a bio when issuing discard commands later. Does this solve the issue with your queue stalls? > > Signed-off-by: Jaegeuk Kim > --- > fs/f2fs/f2fs.h| 4 +- > fs/f2fs/segment.c | 113 >

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

Hi, On Wed, Mar 08, 2017 at 02:42:10PM +0100, Dmitry Vyukov wrote: > I think if we scope compiler atomic builtins to KASAN/KTSAN/KMSAN (and > consequently x86/arm64) initially, it becomes more realistic. For the > tools we don't care about absolute efficiency and this gets rid of > Will's points

Re: [PATCH] f2fs: allocate a bio for discarding when actually issuing it

On Tue, Mar 07, 2017 at 06:33:33PM -0800, Jaegeuk Kim wrote: > Let's allocate a bio when issuing discard commands later. Does this solve the issue with your queue stalls? > > Signed-off-by: Jaegeuk Kim > --- > fs/f2fs/f2fs.h| 4 +- > fs/f2fs/segment.c | 113 >

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

On Wed, Mar 8, 2017 at 4:20 PM, Mark Rutland wrote: > Hi, > > On Wed, Mar 08, 2017 at 02:42:10PM +0100, Dmitry Vyukov wrote: >> I think if we scope compiler atomic builtins to KASAN/KTSAN/KMSAN (and >> consequently x86/arm64) initially, it becomes more realistic. For the >>

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

On Wed, Mar 8, 2017 at 4:20 PM, Mark Rutland wrote: > Hi, > > On Wed, Mar 08, 2017 at 02:42:10PM +0100, Dmitry Vyukov wrote: >> I think if we scope compiler atomic builtins to KASAN/KTSAN/KMSAN (and >> consequently x86/arm64) initially, it becomes more realistic. For the >> tools we don't care

Re: [PATCH 5/5] staging/lustre: Use generic range rwlock

On Tue, 07 Mar 2017, Oleg Drokin wrote: On Mar 7, 2017, at 12:03 AM, Davidlohr Bueso wrote: This replaces the in-house version, which is also derived from Jan's interval tree implementation. Cc: oleg.dro...@intel.com Cc: andreas.dil...@intel.com Cc: jsimm...@infradead.org Cc:

Re: [PATCH 5/5] staging/lustre: Use generic range rwlock

On Tue, 07 Mar 2017, Oleg Drokin wrote: On Mar 7, 2017, at 12:03 AM, Davidlohr Bueso wrote: This replaces the in-house version, which is also derived from Jan's interval tree implementation. Cc: oleg.dro...@intel.com Cc: andreas.dil...@intel.com Cc: jsimm...@infradead.org Cc:

Re: [lkp-robot] [locking/ww_mutex] 857811a371: INFO:task_blocked_for_more_than#seconds

On Wed, Mar 08, 2017 at 12:13:12PM +, Chris Wilson wrote: On Wed, Mar 08, 2017 at 09:08:54AM +0800, kernel test robot wrote: FYI, we noticed the following commit: commit: 857811a37129f5d2ba162d7be3986eff44724014 ("locking/ww_mutex: Adjust the lock number for stress test")

Re: [RFC PATCH v2 02/32] x86: Secure Encrypted Virtualization (SEV) support

On Thu, Mar 02, 2017 at 10:12:20AM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > Provide support for Secure Encyrpted Virtualization (SEV). This initial > support defines a flag that is used by the kernel to determine if it is > running with SEV active. > >

Re: [lkp-robot] [locking/ww_mutex] 857811a371: INFO:task_blocked_for_more_than#seconds

On Wed, Mar 08, 2017 at 12:13:12PM +, Chris Wilson wrote: On Wed, Mar 08, 2017 at 09:08:54AM +0800, kernel test robot wrote: FYI, we noticed the following commit: commit: 857811a37129f5d2ba162d7be3986eff44724014 ("locking/ww_mutex: Adjust the lock number for stress test")

Re: [RFC PATCH v2 02/32] x86: Secure Encrypted Virtualization (SEV) support

On Thu, Mar 02, 2017 at 10:12:20AM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > Provide support for Secure Encyrpted Virtualization (SEV). This initial > support defines a flag that is used by the kernel to determine if it is > running with SEV active. > > Signed-off-by: Tom Lendacky >

[PATCH v3 0/3] Bind RMI4 over SMBus from PS/2

Hi Dmitry, This is mostly a resend of the PS/2-SMBus binding (last 3 patches of now 3 years of trial and errors). I integrated both warnings raised by Coccinelle, and squashed 4/3 into 3/3. I really would like your opinion on this solution. If we could have a full cycle in linux-next that would

[PATCH v3 0/3] Bind RMI4 over SMBus from PS/2

Hi Dmitry, This is mostly a resend of the PS/2-SMBus binding (last 3 patches of now 3 years of trial and errors). I integrated both warnings raised by Coccinelle, and squashed 4/3 into 3/3. I really would like your opinion on this solution. If we could have a full cycle in linux-next that would

Re: [PATCH 6/7] mm: convert generic code to 5-level paging

On Wed, Mar 08, 2017 at 02:57:35PM +0100, Michal Hocko wrote: > On Mon 06-03-17 23:45:13, Kirill A. Shutemov wrote: > > Convert all non-architecture-specific code to 5-level paging. > > > > It's mostly mechanical adding handling one more page table level in > > places where we deal with pud_t. >

Re: [PATCH 6/7] mm: convert generic code to 5-level paging

On Wed, Mar 08, 2017 at 02:57:35PM +0100, Michal Hocko wrote: > On Mon 06-03-17 23:45:13, Kirill A. Shutemov wrote: > > Convert all non-architecture-specific code to 5-level paging. > > > > It's mostly mechanical adding handling one more page table level in > > places where we deal with pud_t. >

[PATCH] fat: Fix using uninitialized fields of fat_inode/fsinfo_inode

Recently fallocate patch was merged and it uses MSDOS_I(inode)->mmu_private at fat_evict_inode(). However, fat_inode/fsinfo_inode that was introduced in past didn't initialize MSDOS_I(inode) properly. With those combinations, it became the cause of accessing random entry in FAT area.

Re: [PATCH v3 4/6] drm: bridge: dw-hdmi: Switch to V4L bus format and encodings

On 03/07/2017 06:35 PM, Jose Abreu wrote: > Hi Neil, > > > On 07-03-2017 16:42, Neil Armstrong wrote: >> Some display pipelines can only provide non-RBG input pixels to the HDMI TX >> Controller, this patch takes the pixel format from the plat_data if provided. >> >> Signed-off-by: Neil

[PATCH v3 1/2] net: sched: make default fifo qdiscs appear in the dump

From: Jiri Kosina The original reason [1] for having hidden qdiscs (potential scalability issues in qdisc_match_from_root() with single linked list in case of large amount of qdiscs) has been invalidated by 59cc1f61f0 ("net: sched: convert qdisc linked list to hashtable"). This

[PATCH] fat: Fix using uninitialized fields of fat_inode/fsinfo_inode

Recently fallocate patch was merged and it uses MSDOS_I(inode)->mmu_private at fat_evict_inode(). However, fat_inode/fsinfo_inode that was introduced in past didn't initialize MSDOS_I(inode) properly. With those combinations, it became the cause of accessing random entry in FAT area.

Re: [PATCH v3 4/6] drm: bridge: dw-hdmi: Switch to V4L bus format and encodings

On 03/07/2017 06:35 PM, Jose Abreu wrote: > Hi Neil, > > > On 07-03-2017 16:42, Neil Armstrong wrote: >> Some display pipelines can only provide non-RBG input pixels to the HDMI TX >> Controller, this patch takes the pixel format from the plat_data if provided. >> >> Signed-off-by: Neil

[PATCH v3 1/2] net: sched: make default fifo qdiscs appear in the dump

From: Jiri Kosina The original reason [1] for having hidden qdiscs (potential scalability issues in qdisc_match_from_root() with single linked list in case of large amount of qdiscs) has been invalidated by 59cc1f61f0 ("net: sched: convert qdisc linked list to hashtable"). This allows us for

Re: [PATCH 22/26] IB/ocrdma: Returning only value constants in ocrdma_resize_cq()

Acked-By:Devesh Sharma On Wed, Mar 8, 2017 at 6:56 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 8 Mar 2017 10:48:24 +0100 > > Return constant integer values without storing them in the

Re: [PATCH 22/26] IB/ocrdma: Returning only value constants in ocrdma_resize_cq()

Acked-By:Devesh Sharma On Wed, Mar 8, 2017 at 6:56 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 8 Mar 2017 10:48:24 +0100 > > Return constant integer values without storing them in the local > variable "status". > > Signed-off-by: Markus Elfring > --- >

Re: [PATCH v2 1/2] net: sched: make default fifo qdiscs appear in the dump

On Wed, 2017-03-08 at 13:03 +0100, Jiri Kosina wrote: > +++ b/net/sched/sch_qfq.c > @@ -494,6 +494,8 @@ static int qfq_change_class(struct Qdisc *sch, u32 > classid, u32 parentid, > goto destroy_class; > } > > + if (cl->qdisc != _qdisc) > +

Re: [PATCH v2 1/2] net: sched: make default fifo qdiscs appear in the dump

On Wed, 2017-03-08 at 13:03 +0100, Jiri Kosina wrote: > +++ b/net/sched/sch_qfq.c > @@ -494,6 +494,8 @@ static int qfq_change_class(struct Qdisc *sch, u32 > classid, u32 parentid, > goto destroy_class; > } > > + if (cl->qdisc != _qdisc) > +

<    5   6   7   8   9   10   11   12   13   14   >