[PATCH stable-4.1.y] tools include: Add a __fallthrough statement

From: Arnaldo Carvalho de Melo commit b5bf1733d6a391c4e90ea8f8468d83023be74a2a upstream. For cases where implicit fall through case labels are intended, to let us inform that to gcc >= 7: CC /tmp/build/perf/util/string.o util/string.c: In function 'perf_atoll':

[PATCH stable-4.1.y] tools include: Add a __fallthrough statement

From: Arnaldo Carvalho de Melo commit b5bf1733d6a391c4e90ea8f8468d83023be74a2a upstream. For cases where implicit fall through case labels are intended, to let us inform that to gcc >= 7: CC /tmp/build/perf/util/string.o util/string.c: In function 'perf_atoll':

Re: [tip:sched/core] sched/isolation: Document the isolcpus= flags

* Frederic Weisbecker wrote: > 2017-10-27 20:21 UTC+02:00, Ingo Molnar : > > > > * Frederic Weisbecker wrote: > > > >> 2017-10-27 19:06 UTC+02:00, Ingo Molnar : > >> > > >> > * Frederic Weisbecker

Re: [tip:sched/core] sched/isolation: Document the isolcpus= flags

* Frederic Weisbecker wrote: > 2017-10-27 20:21 UTC+02:00, Ingo Molnar : > > > > * Frederic Weisbecker wrote: > > > >> 2017-10-27 19:06 UTC+02:00, Ingo Molnar : > >> > > >> > * Frederic Weisbecker wrote: > >> > > >> >> 2017-10-27 15:58 UTC+02:00, Peter Zijlstra : > >> >> > On Fri, Oct 27,

Re: [PATCH v9 02/29] x86/boot: Relocate definition of the initial state of CR0

On Thu, Oct 26, 2017 at 02:55:13PM +0200, Borislav Petkov wrote: > On Thu, Oct 26, 2017 at 02:02:02AM -0700, Andy Lutomirski wrote: > > I'm assuming that UMIP_REPORTED_CR0 will never change. If CR0 gets a > > new field that we set some day, then I assume that CR0_STATE would add > > that bit but

Re: [PATCH v9 02/29] x86/boot: Relocate definition of the initial state of CR0

On Thu, Oct 26, 2017 at 02:55:13PM +0200, Borislav Petkov wrote: > On Thu, Oct 26, 2017 at 02:02:02AM -0700, Andy Lutomirski wrote: > > I'm assuming that UMIP_REPORTED_CR0 will never change. If CR0 gets a > > new field that we set some day, then I assume that CR0_STATE would add > > that bit but

Re: [PATCH] init/main.c: check for null pointer before calling initcall

On 10/27/2017 11:53 AM, Abderrahmane Benbachir wrote: David Daney a écrit : On 10/27/2017 11:22 AM, Thomas Gleixner wrote: On Fri, 27 Oct 2017, David Daney wrote: On 10/27/2017 09:47 AM, Abderrahmane Benbachir wrote: Simple check to prevent kernel panic when

Re: [PATCH] init/main.c: check for null pointer before calling initcall

On 10/27/2017 11:53 AM, Abderrahmane Benbachir wrote: David Daney a écrit : On 10/27/2017 11:22 AM, Thomas Gleixner wrote: On Fri, 27 Oct 2017, David Daney wrote: On 10/27/2017 09:47 AM, Abderrahmane Benbachir wrote: Simple check to prevent kernel panic when initcall does not exit

Re: [PATCH] init/main.c: check for null pointer before calling initcall

David Daney a écrit : On 10/27/2017 11:22 AM, Thomas Gleixner wrote: On Fri, 27 Oct 2017, David Daney wrote: On 10/27/2017 09:47 AM, Abderrahmane Benbachir wrote: Simple check to prevent kernel panic when initcall does not exit Interesting, under what

Re: [PATCH] init/main.c: check for null pointer before calling initcall

David Daney a écrit : On 10/27/2017 11:22 AM, Thomas Gleixner wrote: On Fri, 27 Oct 2017, David Daney wrote: On 10/27/2017 09:47 AM, Abderrahmane Benbachir wrote: Simple check to prevent kernel panic when initcall does not exit Interesting, under what circumstances do you observe the

Re: [PATCH] PM / QoS: Fix device resume latency PM QoS

On Thu, Oct 26, 2017 at 11:38 AM, Rafael J. Wysocki wrote: > On Wed, Oct 25, 2017 at 10:06 PM, Andy Shevchenko > wrote: >> On Tue, Oct 24, 2017 at 11:49 AM, Rafael J. Wysocki >> wrote: >>> On Tuesday, October 24, 2017 7:54:09 AM

Re: [PATCH] PM / QoS: Fix device resume latency PM QoS

On Thu, Oct 26, 2017 at 11:38 AM, Rafael J. Wysocki wrote: > On Wed, Oct 25, 2017 at 10:06 PM, Andy Shevchenko > wrote: >> On Tue, Oct 24, 2017 at 11:49 AM, Rafael J. Wysocki >> wrote: >>> On Tuesday, October 24, 2017 7:54:09 AM CEST Ramesh Thomas wrote: On 2017-10-20 at 13:27:34 +0200,

Re: [PATCH 03/27] Enforce module signatures if the kernel is locked down

On Thu, 2017-10-19 at 15:50 +0100, David Howells wrote: > If the kernel is locked down, require that all modules have valid > signatures that we can verify. > > Signed-off-by: David Howells > --- > > kernel/module.c |3 ++- > 1 file changed, 2 insertions(+), 1

Re: [PATCH 03/27] Enforce module signatures if the kernel is locked down

On Thu, 2017-10-19 at 15:50 +0100, David Howells wrote: > If the kernel is locked down, require that all modules have valid > signatures that we can verify. > > Signed-off-by: David Howells > --- > > kernel/module.c |3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git

Re: [PATCH 1/2] drm/rcar-du: Use common error handling code in rcar_du_encoders_init()

On Tue, 24 Oct 2017, SF Markus Elfring wrote: > Add a jump target so that a bit of exception handling can be better reused > at the end of this function. > > This issue was detected by using the Coccinelle software. Please also look into the GCC software, which

Re: [PATCH 1/2] drm/rcar-du: Use common error handling code in rcar_du_encoders_init()

On Tue, 24 Oct 2017, SF Markus Elfring wrote: > Add a jump target so that a bit of exception handling can be better reused > at the end of this function. > > This issue was detected by using the Coccinelle software. Please also look into the GCC software, which will detect that your patch does

Re: [tip:sched/core] sched/isolation: Document the isolcpus= flags

2017-10-27 20:21 UTC+02:00, Ingo Molnar : > > * Frederic Weisbecker wrote: > >> 2017-10-27 19:06 UTC+02:00, Ingo Molnar : >> > >> > * Frederic Weisbecker wrote: >> > >> >> 2017-10-27 15:58 UTC+02:00, Peter Zijlstra

Re: [tip:sched/core] sched/isolation: Document the isolcpus= flags

2017-10-27 20:21 UTC+02:00, Ingo Molnar : > > * Frederic Weisbecker wrote: > >> 2017-10-27 19:06 UTC+02:00, Ingo Molnar : >> > >> > * Frederic Weisbecker wrote: >> > >> >> 2017-10-27 15:58 UTC+02:00, Peter Zijlstra : >> >> > On Fri, Oct 27, 2017 at 05:06:25AM -0700, tip-bot for Frederic >> >> >

RE: [PATCH] IB/mlx5: give back valid speed/width even without plugged in SFP module

> -Original Message- > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > ow...@vger.kernel.org] On Behalf Of Thomas Bogendoerfer > Sent: Friday, October 27, 2017 7:30 AM > To: Matan Barak ; Leon Romanovsky > ; Doug Ledford

RE: [PATCH] IB/mlx5: give back valid speed/width even without plugged in SFP module

> -Original Message- > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > ow...@vger.kernel.org] On Behalf Of Thomas Bogendoerfer > Sent: Friday, October 27, 2017 7:30 AM > To: Matan Barak ; Leon Romanovsky > ; Doug Ledford ; linux- > r...@vger.kernel.org;

Re: [PATCH v10 1/9] LIB: Introduce a generic PIO mapping method

On 10/27/2017 11:11 AM, Gabriele Paoloni wrote: From: "zhichang.yuan" In commit 41f8bba7f555 ("of/pci: Add pci_register_io_range() and pci_pio_to_address()"), a new I/O space management was supported. With that driver, the I/O ranges configured for PCI/PCIE hosts on

Re: [PATCH v10 1/9] LIB: Introduce a generic PIO mapping method

On 10/27/2017 11:11 AM, Gabriele Paoloni wrote: From: "zhichang.yuan" In commit 41f8bba7f555 ("of/pci: Add pci_register_io_range() and pci_pio_to_address()"), a new I/O space management was supported. With that driver, the I/O ranges configured for PCI/PCIE hosts on some architectures can be

Re: [PATCH] fpga: fpga-mgr: remove unnecessary code in __fpga_mgr_get

On Thu, Oct 26, 2017 at 6:02 PM, Gustavo A. R. Silva wrote: Hi Gustavo, Thanks for pointing that out. There's also a similar thing in fpga-bridge.c that I need to fix. Alan > Notice that mgr = to_fpga_manager(dev); expands to: > > mgr = container_of(dev, struct

Re: [PATCH] fpga: fpga-mgr: remove unnecessary code in __fpga_mgr_get

On Thu, Oct 26, 2017 at 6:02 PM, Gustavo A. R. Silva wrote: Hi Gustavo, Thanks for pointing that out. There's also a similar thing in fpga-bridge.c that I need to fix. Alan > Notice that mgr = to_fpga_manager(dev); expands to: > > mgr = container_of(dev, struct fpga_manager, dev); > > and

Re: [PATCH] kbuild: fix linker feature test macros when cross compiling with Clang

+ linux-kbu...@vger.kernel.org On Fri, Oct 27, 2017 at 4:20 AM, Masahiro Yamada wrote: > I do not like to add $(CLANG_TARGET) to a place for common helpers. > Instead of $(CLANG_TARGET), please add > $(KBUILD_CPPFLAGS) $(CC_OPTION_CFLAGS) > to cc-ldoption and

Re: [PATCH] kbuild: fix linker feature test macros when cross compiling with Clang

+ linux-kbu...@vger.kernel.org On Fri, Oct 27, 2017 at 4:20 AM, Masahiro Yamada wrote: > I do not like to add $(CLANG_TARGET) to a place for common helpers. > Instead of $(CLANG_TARGET), please add > $(KBUILD_CPPFLAGS) $(CC_OPTION_CFLAGS) > to cc-ldoption and ld-option. Thanks for the review.

Re: [PATCH v2] KVM: arm/arm64: Fix external abort type matching

On Fri, Oct 27 2017 at 3:43:26 pm GMT, gengdongjiu wrote: >> >> On Thu, Oct 26 2017 at 6:07:01 pm BST, Dongjiu Geng >> wrote: >> > For this matching, current code using the {I,D}FSC range to match >> > kvm_vcpu_trap_get_fault_type() return

Re: [PATCH v2] KVM: arm/arm64: Fix external abort type matching

On Fri, Oct 27 2017 at 3:43:26 pm GMT, gengdongjiu wrote: >> >> On Thu, Oct 26 2017 at 6:07:01 pm BST, Dongjiu Geng >> wrote: >> > For this matching, current code using the {I,D}FSC range to match >> > kvm_vcpu_trap_get_fault_type() return value, but >> > kvm_vcpu_trap_get_fault_type() only

Re: [PATCH] fpga: region: release of_parse_phandle nodes after use

On Fri, Oct 27, 2017 at 11:56 AM, Ian Abbott wrote: Hi Ian, Looks good. Thanks for catching this! Alan > Both fpga_region_get_manager() and fpga_region_get_bridges() call > of_parse_phandle(), but nothing calls of_node_put() on the returned > struct device_node pointers.

Re: [PATCH] fpga: region: release of_parse_phandle nodes after use

On Fri, Oct 27, 2017 at 11:56 AM, Ian Abbott wrote: Hi Ian, Looks good. Thanks for catching this! Alan > Both fpga_region_get_manager() and fpga_region_get_bridges() call > of_parse_phandle(), but nothing calls of_node_put() on the returned > struct device_node pointers. Make sure to do

Re: [PATCH] init/main.c: check for null pointer before calling initcall

On 10/27/2017 11:22 AM, Thomas Gleixner wrote: On Fri, 27 Oct 2017, David Daney wrote: On 10/27/2017 09:47 AM, Abderrahmane Benbachir wrote: Simple check to prevent kernel panic when initcall does not exit Interesting, under what circumstances do you observe the panic? It would be best to

Re: [PATCH] init/main.c: check for null pointer before calling initcall

On 10/27/2017 11:22 AM, Thomas Gleixner wrote: On Fri, 27 Oct 2017, David Daney wrote: On 10/27/2017 09:47 AM, Abderrahmane Benbachir wrote: Simple check to prevent kernel panic when initcall does not exit Interesting, under what circumstances do you observe the panic? It would be best to

Re: [PATCH] init/main.c: check for null pointer before calling initcall

On Fri, 27 Oct 2017, David Daney wrote: > On 10/27/2017 09:47 AM, Abderrahmane Benbachir wrote: > > Simple check to prevent kernel panic when initcall does not exit > > Interesting, under what circumstances do you observe the panic? > > It would be best to include this information in the patch

Re: [PATCH] init/main.c: check for null pointer before calling initcall

On Fri, 27 Oct 2017, David Daney wrote: > On 10/27/2017 09:47 AM, Abderrahmane Benbachir wrote: > > Simple check to prevent kernel panic when initcall does not exit > > Interesting, under what circumstances do you observe the panic? > > It would be best to include this information in the patch

[PATCH v2] fs: fsnotify: account fsnotify metadata to kmemcg

If some process generates events into a huge or unlimit event queue, but no listener read them, they may consume significant amount of memory silently until oom happens or some memory pressure issue is raised. It'd better to account those slab caches in memcg so that we can get heads up before the

[PATCH v2] fs: fsnotify: account fsnotify metadata to kmemcg

If some process generates events into a huge or unlimit event queue, but no listener read them, they may consume significant amount of memory silently until oom happens or some memory pressure issue is raised. It'd better to account those slab caches in memcg so that we can get heads up before the

Re: [tip:sched/core] sched/isolation: Document the isolcpus= flags

* Frederic Weisbecker wrote: > 2017-10-27 19:06 UTC+02:00, Ingo Molnar : > > > > * Frederic Weisbecker wrote: > > > >> 2017-10-27 15:58 UTC+02:00, Peter Zijlstra : > >> > On Fri, Oct 27, 2017 at 05:06:25AM -0700,

Re: [tip:sched/core] sched/isolation: Document the isolcpus= flags

* Frederic Weisbecker wrote: > 2017-10-27 19:06 UTC+02:00, Ingo Molnar : > > > > * Frederic Weisbecker wrote: > > > >> 2017-10-27 15:58 UTC+02:00, Peter Zijlstra : > >> > On Fri, Oct 27, 2017 at 05:06:25AM -0700, tip-bot for Frederic > >> > Weisbecker > >> > wrote: > >> >> + isolcpus=

Re: [PATCH 14/18] x86/boot/64: Stop initializing TSS.sp0 at boot

On 10/26/2017 01:26 AM, Andy Lutomirski wrote: > --- a/arch/x86/kernel/process.c > +++ b/arch/x86/kernel/process.c > @@ -48,7 +48,8 @@ > */ > __visible DEFINE_PER_CPU_SHARED_ALIGNED(struct tss_struct, cpu_tss) = { > .x86_tss = { > - .sp0 = TOP_OF_INIT_STACK, > + /*

Re: [PATCH 14/18] x86/boot/64: Stop initializing TSS.sp0 at boot

On 10/26/2017 01:26 AM, Andy Lutomirski wrote: > --- a/arch/x86/kernel/process.c > +++ b/arch/x86/kernel/process.c > @@ -48,7 +48,8 @@ > */ > __visible DEFINE_PER_CPU_SHARED_ALIGNED(struct tss_struct, cpu_tss) = { > .x86_tss = { > - .sp0 = TOP_OF_INIT_STACK, > + /*

Re: [PATCH v8 1/5] serdev: Make .remove in struct serdev_device_driver optional

Hi, On Sat, Oct 21, 2017 at 10:08:40AM -0700, Guenter Roeck wrote: > On 10/18/2017 10:01 AM, Andrey Smirnov wrote: > > Using devres infrastructure it is possible to wirte a serdev driver > > s/wirte/write/ > > otherwise > > Reviewed-by: Guenter Roeck Reviewed-by:

Re: [PATCH v8 1/5] serdev: Make .remove in struct serdev_device_driver optional

Hi, On Sat, Oct 21, 2017 at 10:08:40AM -0700, Guenter Roeck wrote: > On 10/18/2017 10:01 AM, Andrey Smirnov wrote: > > Using devres infrastructure it is possible to wirte a serdev driver > > s/wirte/write/ > > otherwise > > Reviewed-by: Guenter Roeck Reviewed-by: Sebastian Reichel --

Re: [PATCH 03/18] x86/asm/64: Move SWAPGS into the common iret-to-usermode path

On 10/26/2017 01:26 AM, Andy Lutomirski wrote: > diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S > index 493e5e234d36..1909a4e42b81 100644 > --- a/arch/x86/entry/entry_64.S > +++ b/arch/x86/entry/entry_64.S > @@ -254,7 +254,7 @@ return_from_SYSCALL_64: > movqRCX(%rsp),

Re: [PATCH 03/18] x86/asm/64: Move SWAPGS into the common iret-to-usermode path

On 10/26/2017 01:26 AM, Andy Lutomirski wrote: > diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S > index 493e5e234d36..1909a4e42b81 100644 > --- a/arch/x86/entry/entry_64.S > +++ b/arch/x86/entry/entry_64.S > @@ -254,7 +254,7 @@ return_from_SYSCALL_64: > movqRCX(%rsp),

Re: [PATCH 02/18] x86/asm/64: Split the iret-to-user and iret-to-kernel paths

On 10/26/2017 01:26 AM, Andy Lutomirski wrote: > +GLOBAL(restore_regs_and_return_to_usermode) > +#ifdef CONFIG_DEBUG_ENTRY > + testl $3, CS(%rsp) > + jnz 1f > + ud2 A nit from the mere mortals in the audience: Could we start commenting or make a constant for the user segment

Re: [PATCH 02/18] x86/asm/64: Split the iret-to-user and iret-to-kernel paths

On 10/26/2017 01:26 AM, Andy Lutomirski wrote: > +GLOBAL(restore_regs_and_return_to_usermode) > +#ifdef CONFIG_DEBUG_ENTRY > + testl $3, CS(%rsp) > + jnz 1f > + ud2 A nit from the mere mortals in the audience: Could we start commenting or make a constant for the user segment

Re: misc: bh1770glc: Use common error handling code in bh1770_power_state_store()

>> Adjust jump targets so that a bit of exception handling can be better >> reused in an if branch of this function. > > What is the benefit brought by this change? Will you notice that the object code size can be a bit smaller because the call of the function “pm_runtime_put” is specified at

Re: misc: bh1770glc: Use common error handling code in bh1770_power_state_store()

>> Adjust jump targets so that a bit of exception handling can be better >> reused in an if branch of this function. > > What is the benefit brought by this change? Will you notice that the object code size can be a bit smaller because the call of the function “pm_runtime_put” is specified at

Re: [PATCH] init/main.c: check for null pointer before calling initcall

On 10/27/2017 09:47 AM, Abderrahmane Benbachir wrote: Simple check to prevent kernel panic when initcall does not exit Interesting, under what circumstances do you observe the panic? It would be best to include this information in the patch changelog. Signed-off-by: Abderrahmane Benbachir

Re: [PATCH] init/main.c: check for null pointer before calling initcall

On 10/27/2017 09:47 AM, Abderrahmane Benbachir wrote: Simple check to prevent kernel panic when initcall does not exit Interesting, under what circumstances do you observe the panic? It would be best to include this information in the patch changelog. Signed-off-by: Abderrahmane Benbachir

Re: [PATCHv1 00/14] omapdrm: DSI command mode panel support

Hi, On Thu, Oct 26, 2017 at 02:59:10PM +0300, Tomi Valkeinen wrote: > On 24/10/17 01:01, Sebastian Reichel wrote: > > Hi, > > > > On Fri, Oct 13, 2017 at 10:12:08AM -0700, Tony Lindgren wrote: > >> * Tomi Valkeinen [171012 01:46]: > >>> On 29/09/17 16:26, Sebastian

Re: [PATCHv1 00/14] omapdrm: DSI command mode panel support

Hi, On Thu, Oct 26, 2017 at 02:59:10PM +0300, Tomi Valkeinen wrote: > On 24/10/17 01:01, Sebastian Reichel wrote: > > Hi, > > > > On Fri, Oct 13, 2017 at 10:12:08AM -0700, Tony Lindgren wrote: > >> * Tomi Valkeinen [171012 01:46]: > >>> On 29/09/17 16:26, Sebastian Reichel wrote: > Hi Tomi

Re: [PATCH v4] iio : Add cm3218 smbus ara and acpi support

> On asus T100, Capella cm3218 chip is implemented as ambiant light > sensor. This chip expose an smbus ARA protocol device on standard > address 0x0c. The chip is not functional before all alerts are > acknowledged. > On asus T100, this device is enumerated on ACPI bus and the description > give

Re: [PATCH v4] iio : Add cm3218 smbus ara and acpi support

> On asus T100, Capella cm3218 chip is implemented as ambiant light > sensor. This chip expose an smbus ARA protocol device on standard > address 0x0c. The chip is not functional before all alerts are > acknowledged. > On asus T100, this device is enumerated on ACPI bus and the description > give

[PATCH v2] pids: introduce find_get_task_by_vpid helper

There are several functions that do find_task_by_vpid() followed by get_task_struct(). We can use a helper function instead. Signed-off-by: Mike Rapoport --- v2: remove futex_find_get_task() and ptrace_get_task_struct() as Oleg suggested include/linux/sched.h | 5

[PATCH v2] pids: introduce find_get_task_by_vpid helper

There are several functions that do find_task_by_vpid() followed by get_task_struct(). We can use a helper function instead. Signed-off-by: Mike Rapoport --- v2: remove futex_find_get_task() and ptrace_get_task_struct() as Oleg suggested include/linux/sched.h | 5 + kernel/futex.c

[PATCH v2] xen: support 52 bit physical addresses in pv guests

Physical addresses on processors supporting 5 level paging can be up to 52 bits wide. For a Xen pv guest running on such a machine those physical addresses have to be supported in order to be able to use any memory on the machine even if the guest itself does not support 5 level paging. So when

[PATCH v2] xen: support 52 bit physical addresses in pv guests

Physical addresses on processors supporting 5 level paging can be up to 52 bits wide. For a Xen pv guest running on such a machine those physical addresses have to be supported in order to be able to use any memory on the machine even if the guest itself does not support 5 level paging. So when

Re: [tip:sched/core] sched/isolation: Document the isolcpus= flags

2017-10-27 19:06 UTC+02:00, Ingo Molnar : > > * Frederic Weisbecker wrote: > >> 2017-10-27 15:58 UTC+02:00, Peter Zijlstra : >> > On Fri, Oct 27, 2017 at 05:06:25AM -0700, tip-bot for Frederic >> > Weisbecker >> > wrote: >> >> +

Re: [tip:sched/core] sched/isolation: Document the isolcpus= flags

2017-10-27 19:06 UTC+02:00, Ingo Molnar : > > * Frederic Weisbecker wrote: > >> 2017-10-27 15:58 UTC+02:00, Peter Zijlstra : >> > On Fri, Oct 27, 2017 at 05:06:25AM -0700, tip-bot for Frederic >> > Weisbecker >> > wrote: >> >> + isolcpus= [KNL,SMP] Isolate a given set of CPUs from

Re: PROBLEM: Remapping hugepages mappings causes kernel to return EINVAL

On Fri, Oct 27, 2017 at 04:29:16PM +0200, Vlastimil Babka wrote: > On 10/24/2017 09:41 AM, C.Wehrmeyer wrote: > > On 2017-10-23 20:02, Michal Hocko wrote: > >> On Mon 23-10-17 19:52:27, C.Wehrmeyer wrote: > >> [...] > or you can mmap a larger block and > munmap the initial unaligned

Re: PROBLEM: Remapping hugepages mappings causes kernel to return EINVAL

On Fri, Oct 27, 2017 at 04:29:16PM +0200, Vlastimil Babka wrote: > On 10/24/2017 09:41 AM, C.Wehrmeyer wrote: > > On 2017-10-23 20:02, Michal Hocko wrote: > >> On Mon 23-10-17 19:52:27, C.Wehrmeyer wrote: > >> [...] > or you can mmap a larger block and > munmap the initial unaligned

Re: [PATCH][tip] x86/paravirt: Make the virt_spin_lock_key setup after jump_label_init()

On 27/10/17 18:02, Dou Liyang wrote: > Commit: > > 9043442b43b1 ("locking/paravirt: Use new static key for controlling > call of virt_spin_lock()") > > set the static virt_spin_lock_key to a value before jump_label_init() > has been called, which will result in a WARN(). > > Move the

Re: [PATCH][tip] x86/paravirt: Make the virt_spin_lock_key setup after jump_label_init()

On 27/10/17 18:02, Dou Liyang wrote: > Commit: > > 9043442b43b1 ("locking/paravirt: Use new static key for controlling > call of virt_spin_lock()") > > set the static virt_spin_lock_key to a value before jump_label_init() > has been called, which will result in a WARN(). > > Move the

Re: [PATCH][tip] x86/paravirt: Make the virt_spin_lock_key setup after jump_label_init()

On 27/10/17 19:09, Vitaly Kuznetsov wrote: > Boris Petkov writes: > >> On October 27, 2017 6:02:00 PM GMT+02:00, Dou Liyang >> wrote: >>> Commit: >>> >>> 9043442b43b1 ("locking/paravirt: Use new static key for controlling >>> call of

Re: [PATCH][tip] x86/paravirt: Make the virt_spin_lock_key setup after jump_label_init()

On 27/10/17 19:09, Vitaly Kuznetsov wrote: > Boris Petkov writes: > >> On October 27, 2017 6:02:00 PM GMT+02:00, Dou Liyang >> wrote: >>> Commit: >>> >>> 9043442b43b1 ("locking/paravirt: Use new static key for controlling >>> call of virt_spin_lock()") >>> >>> set the static

Re: [PATCH] misc: bh1770glc: Use common error handling code in bh1770_power_state_store()

On Fri, Oct 27, 2017 at 11:11:13AM -0600, Daniele Nicolodi wrote: > On 10/27/17 10:20 AM, SF Markus Elfring wrote: > > From: Markus Elfring > > Date: Fri, 27 Oct 2017 18:00:31 +0200 > > > > Adjust jump targets so that a bit of exception handling can be better > >

Re: [PATCH] misc: bh1770glc: Use common error handling code in bh1770_power_state_store()

On Fri, Oct 27, 2017 at 11:11:13AM -0600, Daniele Nicolodi wrote: > On 10/27/17 10:20 AM, SF Markus Elfring wrote: > > From: Markus Elfring > > Date: Fri, 27 Oct 2017 18:00:31 +0200 > > > > Adjust jump targets so that a bit of exception handling can be better > > reused in an if branch of this

[PATCH] mmc: tmio: Use common error handling code in tmio_mmc_host_probe()

From: Markus Elfring Date: Fri, 27 Oct 2017 19:09:17 +0200 * Add a jump target so that a bit of exception handling can be better reused at the end of this function. * Adjust condition checks. This issue was detected by using the Coccinelle software.

[PATCH] mmc: tmio: Use common error handling code in tmio_mmc_host_probe()

From: Markus Elfring Date: Fri, 27 Oct 2017 19:09:17 +0200 * Add a jump target so that a bit of exception handling can be better reused at the end of this function. * Adjust condition checks. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

Re: [PATCH] misc: bh1770glc: Use common error handling code in bh1770_power_state_store()

On 10/27/17 10:20 AM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 27 Oct 2017 18:00:31 +0200 > > Adjust jump targets so that a bit of exception handling can be better > reused in an if branch of this function. What is the benefit brought by this

Re: [PATCH] misc: bh1770glc: Use common error handling code in bh1770_power_state_store()

On 10/27/17 10:20 AM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 27 Oct 2017 18:00:31 +0200 > > Adjust jump targets so that a bit of exception handling can be better > reused in an if branch of this function. What is the benefit brought by this change? Anyhow, are you

Re: [PATCH][tip] x86/paravirt: Make the virt_spin_lock_key setup after jump_label_init()

Boris Petkov writes: > On October 27, 2017 6:02:00 PM GMT+02:00, Dou Liyang > wrote: >>Commit: >> >> 9043442b43b1 ("locking/paravirt: Use new static key for controlling >> call of virt_spin_lock()") >> >>set the static virt_spin_lock_key to a value

Re: [PATCH][tip] x86/paravirt: Make the virt_spin_lock_key setup after jump_label_init()

Boris Petkov writes: > On October 27, 2017 6:02:00 PM GMT+02:00, Dou Liyang > wrote: >>Commit: >> >> 9043442b43b1 ("locking/paravirt: Use new static key for controlling >> call of virt_spin_lock()") >> >>set the static virt_spin_lock_key to a value before jump_label_init() >>has been called,

Re: [PATCH 0/3] support for Logilink VG0022a DVB-T2 stick

Hello All, I'm responding to this thread because I have a Terretec CINERGY TC2 Stick, similar chips, it9303/si2147/si2168, which shows the same problem. Connecting a scope to the physical i2c bus between 2147 and 2168 gave some suprising results. With probe connected to the sda line, the i2c

Re: [PATCH 0/3] support for Logilink VG0022a DVB-T2 stick

Hello All, I'm responding to this thread because I have a Terretec CINERGY TC2 Stick, similar chips, it9303/si2147/si2168, which shows the same problem. Connecting a scope to the physical i2c bus between 2147 and 2168 gave some suprising results. With probe connected to the sda line, the i2c

Re: [tip:sched/core] sched/isolation: Document the isolcpus= flags

* Frederic Weisbecker wrote: > 2017-10-27 15:58 UTC+02:00, Peter Zijlstra : > > On Fri, Oct 27, 2017 at 05:06:25AM -0700, tip-bot for Frederic Weisbecker > > wrote: > >> + isolcpus= [KNL,SMP] Isolate a given set of CPUs from disturbance. > >> +

Re: [tip:sched/core] sched/isolation: Document the isolcpus= flags

* Frederic Weisbecker wrote: > 2017-10-27 15:58 UTC+02:00, Peter Zijlstra : > > On Fri, Oct 27, 2017 at 05:06:25AM -0700, tip-bot for Frederic Weisbecker > > wrote: > >> + isolcpus= [KNL,SMP] Isolate a given set of CPUs from disturbance. > >> + Format: [flag-list,] > >>

Re: PROBLEM: Remapping hugepages mappings causes kernel to return EINVAL

On 10/27/2017 07:29 AM, Vlastimil Babka wrote: > On 10/24/2017 09:41 AM, C.Wehrmeyer wrote: >> On 2017-10-23 20:02, Michal Hocko wrote: >>> On Mon 23-10-17 19:52:27, C.Wehrmeyer wrote: >>> [...] >> >> 1. Provide a flag to mmap, which might be something different from >> MAP_HUGETLB. After all

Re: PROBLEM: Remapping hugepages mappings causes kernel to return EINVAL

On 10/27/2017 07:29 AM, Vlastimil Babka wrote: > On 10/24/2017 09:41 AM, C.Wehrmeyer wrote: >> On 2017-10-23 20:02, Michal Hocko wrote: >>> On Mon 23-10-17 19:52:27, C.Wehrmeyer wrote: >>> [...] >> >> 1. Provide a flag to mmap, which might be something different from >> MAP_HUGETLB. After all

[PATCH] init/main.c: check for null pointer before calling initcall

Simple check to prevent kernel panic when initcall does not exit Signed-off-by: Abderrahmane Benbachir --- init/main.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/init/main.c b/init/main.c index 0ee9c6866ada..220fd2822b61 100644 --- a/init/main.c

[PATCH] init/main.c: check for null pointer before calling initcall

Simple check to prevent kernel panic when initcall does not exit Signed-off-by: Abderrahmane Benbachir --- init/main.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/init/main.c b/init/main.c index 0ee9c6866ada..220fd2822b61 100644 --- a/init/main.c +++ b/init/main.c @@ -817,6 +817,9 @@

[PATCH] fpga: region: release of_parse_phandle nodes after use

Both fpga_region_get_manager() and fpga_region_get_bridges() call of_parse_phandle(), but nothing calls of_node_put() on the returned struct device_node pointers. Make sure to do that to stop their reference counters getting out of whack. Fixes: 0fa20cdfcc1f ("fpga: fpga-region: device tree

[PATCH] fpga: region: release of_parse_phandle nodes after use

Both fpga_region_get_manager() and fpga_region_get_bridges() call of_parse_phandle(), but nothing calls of_node_put() on the returned struct device_node pointers. Make sure to do that to stop their reference counters getting out of whack. Fixes: 0fa20cdfcc1f ("fpga: fpga-region: device tree

Re: [PATCH] usb: musb_core: mark expected switch fall-through

On Fri, Oct 27, 2017 at 06:49:49PM +0200, Greg Kroah-Hartman wrote: > On Fri, Oct 27, 2017 at 11:44:47AM -0500, Bin Liu wrote: > > Hi, > > > > On Mon, Oct 23, 2017 at 10:10:43PM -0500, Gustavo A. R. Silva wrote: > > > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > > >

Re: [PATCH] usb: musb_core: mark expected switch fall-through

On Fri, Oct 27, 2017 at 06:49:49PM +0200, Greg Kroah-Hartman wrote: > On Fri, Oct 27, 2017 at 11:44:47AM -0500, Bin Liu wrote: > > Hi, > > > > On Mon, Oct 23, 2017 at 10:10:43PM -0500, Gustavo A. R. Silva wrote: > > > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > > >

[PATCH v2] hwmon: (pmbus/core): Prevent unintentional setting of page to 0xFF

From: "Edward A. James" The pmbus core may call read/write word data functions with a page value of -1, intending to perform the operation without setting the page. However, the read/write word data functions accept only unsigned 8-bit page numbers, and therefore cannot check

[PATCH v2] hwmon: (pmbus/core): Prevent unintentional setting of page to 0xFF

From: "Edward A. James" The pmbus core may call read/write word data functions with a page value of -1, intending to perform the operation without setting the page. However, the read/write word data functions accept only unsigned 8-bit page numbers, and therefore cannot check for negative page

Re: [PATCH 1/2] mm: extract common code for calculating total memory size

On 10/27/17 3:00 AM, Christopher Lameter wrote: On Thu, 26 Oct 2017, Yang Shi wrote: diff --git a/include/linux/mm.h b/include/linux/mm.h index 935c4d4..e21b81e 100644 --- a/include/linux/mm.h +++ b/include/linux/mm.h @@ -2050,6 +2050,31 @@ extern int __meminit __early_pfn_to_nid(unsigned

Re: [PATCH 1/2] mm: extract common code for calculating total memory size

On 10/27/17 3:00 AM, Christopher Lameter wrote: On Thu, 26 Oct 2017, Yang Shi wrote: diff --git a/include/linux/mm.h b/include/linux/mm.h index 935c4d4..e21b81e 100644 --- a/include/linux/mm.h +++ b/include/linux/mm.h @@ -2050,6 +2050,31 @@ extern int __meminit __early_pfn_to_nid(unsigned

Re: [PATCH][tip] x86/paravirt: Make the virt_spin_lock_key setup after jump_label_init()

On October 27, 2017 6:02:00 PM GMT+02:00, Dou Liyang wrote: >Commit: > > 9043442b43b1 ("locking/paravirt: Use new static key for controlling > call of virt_spin_lock()") > >set the static virt_spin_lock_key to a value before jump_label_init() >has been called, which

Re: [PATCH][tip] x86/paravirt: Make the virt_spin_lock_key setup after jump_label_init()

On October 27, 2017 6:02:00 PM GMT+02:00, Dou Liyang wrote: >Commit: > > 9043442b43b1 ("locking/paravirt: Use new static key for controlling > call of virt_spin_lock()") > >set the static virt_spin_lock_key to a value before jump_label_init() >has been called, which will result in a WARN(). >

Re: [PATCH] platform/x86: fujitsu-laptop: Fix radio LED detection

On Wed, Oct 25, 2017 at 7:29 AM, Michał Kępień wrote: > Radio LED detection method implemented in commit 4f62568c1fcf > ("fujitsu-laptop: Support radio LED") turned out to be incorrect as it > causes a radio LED to be erroneously detected on a Fujitsu Lifebook E751 > which has

Re: [PATCH] platform/x86: fujitsu-laptop: Fix radio LED detection

On Wed, Oct 25, 2017 at 7:29 AM, Michał Kępień wrote: > Radio LED detection method implemented in commit 4f62568c1fcf > ("fujitsu-laptop: Support radio LED") turned out to be incorrect as it > causes a radio LED to be erroneously detected on a Fujitsu Lifebook E751 > which has a slide switch (and

Re: [PATCH] usb: musb_core: mark expected switch fall-through

On Fri, Oct 27, 2017 at 11:44:47AM -0500, Bin Liu wrote: > Hi, > > On Mon, Oct 23, 2017 at 10:10:43PM -0500, Gustavo A. R. Silva wrote: > > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > > where we are expecting to fall through. > > > > Addresses-Coverity-ID: 1397608 > >

Re: [PATCH] usb: musb_core: mark expected switch fall-through

On Fri, Oct 27, 2017 at 11:44:47AM -0500, Bin Liu wrote: > Hi, > > On Mon, Oct 23, 2017 at 10:10:43PM -0500, Gustavo A. R. Silva wrote: > > In preparation to enabling -Wimplicit-fallthrough, mark switch cases > > where we are expecting to fall through. > > > > Addresses-Coverity-ID: 1397608 > >

Re: [PATCH] platform/x86: silead_dmi: Fix GP-electronic T701 entry

On Thu, Oct 19, 2017 at 10:44 AM, Hans de Goede wrote: > The GP-electronic T701 has its LCD panel mounted upside-down, initially > my plan was to fix this by transparently rotating the image in the i915 > driver (my "drm/i915: Deal with upside-down mounted LCD" patch), but >

Re: [RFC 13/14] bootsplash: Add main documentation

On 10/27/17 04:19, Max Staudt wrote: > On 10/25/2017 07:43 PM, Randy Dunlap wrote: >> On 10/25/17 05:46, Max Staudt wrote: >>> Signed-off-by: Max Staudt >>> Reviewed-by: Oliver Neukum >>> --- >>> Documentation/fb/bootsplash.txt | 169 >>>

Re: [PATCH] platform/x86: silead_dmi: Fix GP-electronic T701 entry

On Thu, Oct 19, 2017 at 10:44 AM, Hans de Goede wrote: > The GP-electronic T701 has its LCD panel mounted upside-down, initially > my plan was to fix this by transparently rotating the image in the i915 > driver (my "drm/i915: Deal with upside-down mounted LCD" patch), but > that approach has

Re: [RFC 13/14] bootsplash: Add main documentation

On 10/27/17 04:19, Max Staudt wrote: > On 10/25/2017 07:43 PM, Randy Dunlap wrote: >> On 10/25/17 05:46, Max Staudt wrote: >>> Signed-off-by: Max Staudt >>> Reviewed-by: Oliver Neukum >>> --- >>> Documentation/fb/bootsplash.txt | 169 >>> >>> 1 file

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