Re: [PATCH] net: stmmac: Avoid VLA usage

On 05/02/2018 04:07 PM, Jose Abreu wrote: On 02-05-2018 13:36, Kees Cook wrote: On Wed, May 2, 2018 at 1:54 AM, Jose Abreu wrote: Hi Kees, On 01-05-2018 22:01, Kees Cook wrote: In the quest to remove all stack VLAs from the kernel[1], this switches the "status"

Re: [PATCH] net: stmmac: Avoid VLA usage

On 05/02/2018 04:07 PM, Jose Abreu wrote: On 02-05-2018 13:36, Kees Cook wrote: On Wed, May 2, 2018 at 1:54 AM, Jose Abreu wrote: Hi Kees, On 01-05-2018 22:01, Kees Cook wrote: In the quest to remove all stack VLAs from the kernel[1], this switches the "status" stack buffer to use the

Re: arch/x86/net/bpf_jit_comp conflicts. was: [tip:x86/cleanups] x86/bpf: Clean up non-standard comments, to make the code more readable

On 04/28/2018 12:16 AM, Alexei Starovoitov wrote: > On 4/27/18 5:13 AM, Daniel Borkmann wrote: >> On 04/27/2018 01:00 PM, tip-bot for Ingo Molnar wrote: >>> Commit-ID:  5f26c50143f58f256535bee8d93a105f36d4d2da >>> Gitweb: >>> https://git.kernel.org/tip/5f26c50143f58f256535bee8d93a105f36d4d2da

Re: arch/x86/net/bpf_jit_comp conflicts. was: [tip:x86/cleanups] x86/bpf: Clean up non-standard comments, to make the code more readable

On 04/28/2018 12:16 AM, Alexei Starovoitov wrote: > On 4/27/18 5:13 AM, Daniel Borkmann wrote: >> On 04/27/2018 01:00 PM, tip-bot for Ingo Molnar wrote: >>> Commit-ID:  5f26c50143f58f256535bee8d93a105f36d4d2da >>> Gitweb: >>> https://git.kernel.org/tip/5f26c50143f58f256535bee8d93a105f36d4d2da

Re: [PATCH 2/2] perf: add arm64 smmuv3 pmu driver

On 2018-04-02 02:37, Yisheng Xie wrote: Hi Neil, On 2018/4/1 13:44, Neil Leeder wrote: Hi Yisheng Xie, On 3/29/2018 03:03 AM, Yisheng Xie wrote: Hi Neil, On 2017/8/5 3:59, Neil Leeder wrote: +mem_resource_0 = platform_get_resource(pdev, IORESOURCE_MEM, 0); +mem_map_0 =

Re: [PATCH 2/2] perf: add arm64 smmuv3 pmu driver

On 2018-04-02 02:37, Yisheng Xie wrote: Hi Neil, On 2018/4/1 13:44, Neil Leeder wrote: Hi Yisheng Xie, On 3/29/2018 03:03 AM, Yisheng Xie wrote: Hi Neil, On 2017/8/5 3:59, Neil Leeder wrote: +mem_resource_0 = platform_get_resource(pdev, IORESOURCE_MEM, 0); +mem_map_0 =

Re: [PATCH] gpio: zynq: Setup chip->base based on alias ID

On 2.5.2018 15:56, Linus Walleij wrote: > On Wed, May 2, 2018 at 3:41 PM, Michal Simek wrote: > >> If you don't want this patch I understand that and it will become just >> another soc vendor patch out of mainline. > > I don't really know what to do, so that is why I'm

Re: [PATCH] gpio: zynq: Setup chip->base based on alias ID

On 2.5.2018 15:56, Linus Walleij wrote: > On Wed, May 2, 2018 at 3:41 PM, Michal Simek wrote: > >> If you don't want this patch I understand that and it will become just >> another soc vendor patch out of mainline. > > I don't really know what to do, so that is why I'm discussing. me too. It

Re: [PATCH v3] module: Fix display of wrong module .text address

On Wed, May 2, 2018 at 1:13 AM, Thomas-Mich Richter wrote: > On 05/02/2018 04:20 AM, Kees Cook wrote: >> On Wed, Apr 18, 2018 at 12:14 AM, Thomas Richter >> wrote: >>> Reading file /proc/modules shows the correct address: >>> [root@s35lp76 ~]# cat

Re: [PATCH v3] module: Fix display of wrong module .text address

On Wed, May 2, 2018 at 1:13 AM, Thomas-Mich Richter wrote: > On 05/02/2018 04:20 AM, Kees Cook wrote: >> On Wed, Apr 18, 2018 at 12:14 AM, Thomas Richter >> wrote: >>> Reading file /proc/modules shows the correct address: >>> [root@s35lp76 ~]# cat /proc/modules | egrep '^qeth_l2' >>> qeth_l2

Re: [PATCH] vhost: make msg padding explicit

On Wed, May 02, 2018 at 10:04:46AM -0400, David Miller wrote: > From: "Michael S. Tsirkin" > Date: Wed, 2 May 2018 16:36:37 +0300 > > > Ouch. True - and in particular the 32 bit ABI on 64 bit kernels doesn't > > work at all. Hmm. It's relatively new and maybe there aren't any

Re: [PATCH v2 5/5] asm-generic: fix build error in fix_to_virt with CONFIG_DEBUG_EXPERIENCE

On Wed, 2 May 2018 21:45:00 +0800 changbin...@intel.com wrote: > From: Changbin Du > > With '-Og' optimization level, GCC would not optimize a count for a loop > as a constant value. But BUILD_BUG_ON() only accept compile-time constant > values. > > arch/arm/mm/mmu.o:

Re: [PATCH] vhost: make msg padding explicit

On Wed, May 02, 2018 at 10:04:46AM -0400, David Miller wrote: > From: "Michael S. Tsirkin" > Date: Wed, 2 May 2018 16:36:37 +0300 > > > Ouch. True - and in particular the 32 bit ABI on 64 bit kernels doesn't > > work at all. Hmm. It's relatively new and maybe there aren't any 32 bit > > users

Re: [PATCH v2 5/5] asm-generic: fix build error in fix_to_virt with CONFIG_DEBUG_EXPERIENCE

On Wed, 2 May 2018 21:45:00 +0800 changbin...@intel.com wrote: > From: Changbin Du > > With '-Og' optimization level, GCC would not optimize a count for a loop > as a constant value. But BUILD_BUG_ON() only accept compile-time constant > values. > > arch/arm/mm/mmu.o: In function

[PATCH] Revert "vhost: make msg padding explicit"

This reverts commit 93c0d549c4c5a7382ad70de6b86610b7aae57406. Unfortunately the padding will break 32 bit userspace. Ouch. Need to add some compat code, revert for now. Signed-off-by: Michael S. Tsirkin --- include/uapi/linux/vhost.h | 1 - 1 file changed, 1 deletion(-) diff

[PATCH] Revert "vhost: make msg padding explicit"

This reverts commit 93c0d549c4c5a7382ad70de6b86610b7aae57406. Unfortunately the padding will break 32 bit userspace. Ouch. Need to add some compat code, revert for now. Signed-off-by: Michael S. Tsirkin --- include/uapi/linux/vhost.h | 1 - 1 file changed, 1 deletion(-) diff --git

Re: [PATCH v2 4/5] kernel hacking: new config DEBUG_EXPERIENCE to apply GCC -Og optimization

On Wed, 2 May 2018 21:44:59 +0800 changbin...@intel.com wrote: > From: Changbin Du > > This will apply GCC '-Og' optimization level which is supported > since GCC 4.8. This optimization level offers a reasonable level > of optimization while maintaining fast compilation

Re: [PATCH v2 4/5] kernel hacking: new config DEBUG_EXPERIENCE to apply GCC -Og optimization

On Wed, 2 May 2018 21:44:59 +0800 changbin...@intel.com wrote: > From: Changbin Du > > This will apply GCC '-Og' optimization level which is supported > since GCC 4.8. This optimization level offers a reasonable level > of optimization while maintaining fast compilation and a good > debugging

Re: [PATCH v10 00/25] Speculative page faults

Hi Laurent, One query below - Laurent Dufour writes: [...] > > Ebizzy: > --- > The test is counting the number of records per second it can manage, the > higher is the best. I run it like this 'ebizzy -mTRp'. To get consistent > result I repeated the test 100

Re: [PATCH v10 00/25] Speculative page faults

Hi Laurent, One query below - Laurent Dufour writes: [...] > > Ebizzy: > --- > The test is counting the number of records per second it can manage, the > higher is the best. I run it like this 'ebizzy -mTRp'. To get consistent > result I repeated the test 100 times and measure the average

[tip:timers/urgent] clocksource: Rework stale comment

Commit-ID: 7dba33c6346c337aac3f7cd188137d4a6d3d1f3a Gitweb: https://git.kernel.org/tip/7dba33c6346c337aac3f7cd188137d4a6d3d1f3a Author: Peter Zijlstra AuthorDate: Mon, 30 Apr 2018 12:00:14 +0200 Committer: Thomas Gleixner CommitDate: Wed, 2 May

[tip:timers/urgent] clocksource: Rework stale comment

Commit-ID: 7dba33c6346c337aac3f7cd188137d4a6d3d1f3a Gitweb: https://git.kernel.org/tip/7dba33c6346c337aac3f7cd188137d4a6d3d1f3a Author: Peter Zijlstra AuthorDate: Mon, 30 Apr 2018 12:00:14 +0200 Committer: Thomas Gleixner CommitDate: Wed, 2 May 2018 16:10:41 +0200 clocksource: Rework

Re: [RFC][PATCH] memcg: Replace mm->owner with mm->memcg

Johannes Weiner writes: > Hi Eric, > > On Wed, May 02, 2018 at 10:47:08AM +0200, Michal Hocko wrote: >> [CC johannes and Tejun as well. I am sorry but my backlog is so huge I >> will not get to this week.] >> >> On Tue 01-05-18 12:35:16, Eric W. Biederman wrote: >> >

Re: [RFC][PATCH] memcg: Replace mm->owner with mm->memcg

Johannes Weiner writes: > Hi Eric, > > On Wed, May 02, 2018 at 10:47:08AM +0200, Michal Hocko wrote: >> [CC johannes and Tejun as well. I am sorry but my backlog is so huge I >> will not get to this week.] >> >> On Tue 01-05-18 12:35:16, Eric W. Biederman wrote: >> > Recently it was reported

[tip:timers/urgent] clocksource: Consistent de-rate when marking unstable

Commit-ID: cd2af07d823e5287cd6c91d54337348c2a873462 Gitweb: https://git.kernel.org/tip/cd2af07d823e5287cd6c91d54337348c2a873462 Author: Peter Zijlstra AuthorDate: Mon, 30 Apr 2018 12:00:13 +0200 Committer: Thomas Gleixner CommitDate: Wed, 2 May

[tip:timers/urgent] clocksource: Consistent de-rate when marking unstable

Commit-ID: cd2af07d823e5287cd6c91d54337348c2a873462 Gitweb: https://git.kernel.org/tip/cd2af07d823e5287cd6c91d54337348c2a873462 Author: Peter Zijlstra AuthorDate: Mon, 30 Apr 2018 12:00:13 +0200 Committer: Thomas Gleixner CommitDate: Wed, 2 May 2018 16:10:41 +0200 clocksource:

[tip:timers/urgent] x86/tsc: Fix mark_tsc_unstable()

Commit-ID: e3b4f79025e0a4eb7e2a2c7d24dadfa1e38893b0 Gitweb: https://git.kernel.org/tip/e3b4f79025e0a4eb7e2a2c7d24dadfa1e38893b0 Author: Peter Zijlstra AuthorDate: Mon, 30 Apr 2018 12:00:12 +0200 Committer: Thomas Gleixner CommitDate: Wed, 2 May

[PATCH v2] thermal: ti-soc-thermal: fix incorrect entry in omap5430_adc_to_temp[]

Entry for Index 941 has one zero too much. Fix it. Signed-off-by: Bartlomiej Zolnierkiewicz --- v2: - Fix patch description. drivers/thermal/ti-soc-thermal/omap5-thermal-data.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index:

[tip:timers/urgent] x86/tsc: Fix mark_tsc_unstable()

Commit-ID: e3b4f79025e0a4eb7e2a2c7d24dadfa1e38893b0 Gitweb: https://git.kernel.org/tip/e3b4f79025e0a4eb7e2a2c7d24dadfa1e38893b0 Author: Peter Zijlstra AuthorDate: Mon, 30 Apr 2018 12:00:12 +0200 Committer: Thomas Gleixner CommitDate: Wed, 2 May 2018 16:10:40 +0200 x86/tsc: Fix

[PATCH v2] thermal: ti-soc-thermal: fix incorrect entry in omap5430_adc_to_temp[]

Entry for Index 941 has one zero too much. Fix it. Signed-off-by: Bartlomiej Zolnierkiewicz --- v2: - Fix patch description. drivers/thermal/ti-soc-thermal/omap5-thermal-data.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index:

[tip:timers/urgent] clocksource: Initialize cs->wd_list

Commit-ID: 5b9e886a4af97574ca3ce1147f35545da0e7afc7 Gitweb: https://git.kernel.org/tip/5b9e886a4af97574ca3ce1147f35545da0e7afc7 Author: Peter Zijlstra AuthorDate: Mon, 30 Apr 2018 12:00:11 +0200 Committer: Thomas Gleixner CommitDate: Wed, 2 May

[tip:timers/urgent] clocksource: Initialize cs->wd_list

Commit-ID: 5b9e886a4af97574ca3ce1147f35545da0e7afc7 Gitweb: https://git.kernel.org/tip/5b9e886a4af97574ca3ce1147f35545da0e7afc7 Author: Peter Zijlstra AuthorDate: Mon, 30 Apr 2018 12:00:11 +0200 Committer: Thomas Gleixner CommitDate: Wed, 2 May 2018 16:10:40 +0200 clocksource:

[tip:timers/urgent] clocksource: Allow clocksource_mark_unstable() on unregistered clocksources

Commit-ID: 2aae7bcfa4104b770e6f612356adb8d66c6144d6 Gitweb: https://git.kernel.org/tip/2aae7bcfa4104b770e6f612356adb8d66c6144d6 Author: Peter Zijlstra AuthorDate: Mon, 23 Apr 2018 17:28:55 +0200 Committer: Thomas Gleixner CommitDate: Wed, 2 May

[tip:timers/urgent] clocksource: Allow clocksource_mark_unstable() on unregistered clocksources

Commit-ID: 2aae7bcfa4104b770e6f612356adb8d66c6144d6 Gitweb: https://git.kernel.org/tip/2aae7bcfa4104b770e6f612356adb8d66c6144d6 Author: Peter Zijlstra AuthorDate: Mon, 23 Apr 2018 17:28:55 +0200 Committer: Thomas Gleixner CommitDate: Wed, 2 May 2018 16:10:40 +0200 clocksource: Allow

[tip:timers/urgent] x86/tsc: Always unregister clocksource_tsc_early

Commit-ID: e9088adda13cd23249d4b0abb97ff8a81bf5573a Gitweb: https://git.kernel.org/tip/e9088adda13cd23249d4b0abb97ff8a81bf5573a Author: Peter Zijlstra AuthorDate: Mon, 30 Apr 2018 12:00:09 +0200 Committer: Thomas Gleixner CommitDate: Wed, 2 May

[tip:timers/urgent] x86/tsc: Always unregister clocksource_tsc_early

Commit-ID: e9088adda13cd23249d4b0abb97ff8a81bf5573a Gitweb: https://git.kernel.org/tip/e9088adda13cd23249d4b0abb97ff8a81bf5573a Author: Peter Zijlstra AuthorDate: Mon, 30 Apr 2018 12:00:09 +0200 Committer: Thomas Gleixner CommitDate: Wed, 2 May 2018 16:10:40 +0200 x86/tsc: Always

[PATCH] ARM: dts: BCM5301X: Relicense most DTS files to the GPL 2.0+ / MIT

From: Rafał Miłecki These files were created and ever touched by a group of three people only: Dan, Hauke and me. They were licensed under GNU/GPL or ISC. Introducing and discussing SPDX-License-Identifier resulted in a conclusion that ISC is a not recommended license (see

[PATCH] ARM: dts: BCM5301X: Relicense most DTS files to the GPL 2.0+ / MIT

From: Rafał Miłecki These files were created and ever touched by a group of three people only: Dan, Hauke and me. They were licensed under GNU/GPL or ISC. Introducing and discussing SPDX-License-Identifier resulted in a conclusion that ISC is a not recommended license (see also a

Re: [PATCH -next] user_namespace: Replace gotos with return statements

On Wed, Apr 18, 2018 at 11:46:38PM -0300, Marcos Paulo de Souza wrote: > Found while inspecting the code that handles the setgroups procfs file. This is not really improving anything so I unfortunately don't really see why we should take this. Christian > > Signed-off-by: Marcos Paulo de Souza

Re: [PATCH -next] user_namespace: Replace gotos with return statements

On Wed, Apr 18, 2018 at 11:46:38PM -0300, Marcos Paulo de Souza wrote: > Found while inspecting the code that handles the setgroups procfs file. This is not really improving anything so I unfortunately don't really see why we should take this. Christian > > Signed-off-by: Marcos Paulo de Souza

Re: WARNING in sysfs_remove_group

syzbot has hit this bug for nearly 6000 times. Why not to fix this trivial one? ;-) >From 626d33de1b70b11ecaf95a9f83f7644998e54cbb Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Wed, 2 May 2018 23:03:48 +0900 Subject: [PATCH] loop: remember whether

Re: WARNING in sysfs_remove_group

syzbot has hit this bug for nearly 6000 times. Why not to fix this trivial one? ;-) >From 626d33de1b70b11ecaf95a9f83f7644998e54cbb Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Wed, 2 May 2018 23:03:48 +0900 Subject: [PATCH] loop: remember whether sysfs_create_group() succeeded syzbot is

Re: [PATCH v7 3/5] cpuset: Add a root-only cpus.isolated v2 control file

On Thu, Apr 19, 2018 at 09:47:02AM -0400, Waiman Long wrote: > diff --git a/Documentation/cgroup-v2.txt b/Documentation/cgroup-v2.txt > index c970bd7..8d89dc2 100644 > --- a/Documentation/cgroup-v2.txt > +++ b/Documentation/cgroup-v2.txt > @@ -1484,6 +1484,31 @@ Cpuset Interface Files > a

Re: [PATCH v7 3/5] cpuset: Add a root-only cpus.isolated v2 control file

On Thu, Apr 19, 2018 at 09:47:02AM -0400, Waiman Long wrote: > diff --git a/Documentation/cgroup-v2.txt b/Documentation/cgroup-v2.txt > index c970bd7..8d89dc2 100644 > --- a/Documentation/cgroup-v2.txt > +++ b/Documentation/cgroup-v2.txt > @@ -1484,6 +1484,31 @@ Cpuset Interface Files > a

Re: [PATCH 2/2] arm64/mm: add speculative page fault

Hi Ganesh, Thank you for the patch! Yet something to improve: [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.17-rc3 next-20180502] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: [PATCH 2/2] arm64/mm: add speculative page fault

Hi Ganesh, Thank you for the patch! Yet something to improve: [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.17-rc3 next-20180502] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: [PATCH] net: stmmac: Avoid VLA usage

On 02-05-2018 13:36, Kees Cook wrote: > On Wed, May 2, 2018 at 1:54 AM, Jose Abreu wrote: >> Hi Kees, >> >> On 01-05-2018 22:01, Kees Cook wrote: >>> In the quest to remove all stack VLAs from the kernel[1], this switches >>> the "status" stack buffer to use the

Re: [PATCH] net: stmmac: Avoid VLA usage

On 02-05-2018 13:36, Kees Cook wrote: > On Wed, May 2, 2018 at 1:54 AM, Jose Abreu wrote: >> Hi Kees, >> >> On 01-05-2018 22:01, Kees Cook wrote: >>> In the quest to remove all stack VLAs from the kernel[1], this switches >>> the "status" stack buffer to use the existing small (8) upper bound

Re: [PATCH v2 3/5] kernel hacking: new config NO_AUTO_INLINE to disable compiler auto-inline optimizations

On Wed, 2 May 2018 21:44:58 +0800 changbin...@intel.com wrote: > From: Changbin Du > > This patch add a new kernel hacking option NO_AUTO_INLINE. Selecting > this option will prevent the compiler from optimizing the kernel by > auto-inlining functions not marked with the

Re: [PATCH v2 3/5] kernel hacking: new config NO_AUTO_INLINE to disable compiler auto-inline optimizations

On Wed, 2 May 2018 21:44:58 +0800 changbin...@intel.com wrote: > From: Changbin Du > > This patch add a new kernel hacking option NO_AUTO_INLINE. Selecting > this option will prevent the compiler from optimizing the kernel by > auto-inlining functions not marked with the inline keyword. > >

Re: [PATCH] typec: tcpm: Fix incorrect 'and' operator

On Mon, Apr 30, 2018 at 08:23:06AM -0500, Gustavo A. R. Silva wrote: > Currently, logical and is being used instead of *bitwise* and. > > Fix this by using a proper bitwise and operator. > > Addresses-Coverity-ID: 1468455 ("Logical vs. bitwise operator") > Fixes: 64f7c494a3c0 ("typec: tcpm: Add

Re: [PATCH] typec: tcpm: Fix incorrect 'and' operator

On Mon, Apr 30, 2018 at 08:23:06AM -0500, Gustavo A. R. Silva wrote: > Currently, logical and is being used instead of *bitwise* and. > > Fix this by using a proper bitwise and operator. > > Addresses-Coverity-ID: 1468455 ("Logical vs. bitwise operator") > Fixes: 64f7c494a3c0 ("typec: tcpm: Add

Re: [PATCH 1/2] selftests/filesystems: devpts_pts included wrong header

On Wed, Apr 18, 2018 at 09:52:55AM +0200, Anders Roxell wrote: > We were picking up the wrong header should use asm/ioctls.h form the kernel > and not the header from the system (sys/ioctl.h). In the current code we > added the correct include and we added the kernel headers path to the CFLAGS. >

Re: [PATCH 1/2] selftests/filesystems: devpts_pts included wrong header

On Wed, Apr 18, 2018 at 09:52:55AM +0200, Anders Roxell wrote: > We were picking up the wrong header should use asm/ioctls.h form the kernel > and not the header from the system (sys/ioctl.h). In the current code we > added the correct include and we added the kernel headers path to the CFLAGS. >

Re: [PATCH 26/28] venus: implementing multi-stream support

On 2018-05-02 18:58, Nicolas Dufresne wrote: Le mercredi 02 mai 2018 à 13:10 +0530, Vikash Garodia a écrit : Hello Stanimir, On 2018-04-24 18:14, Stanimir Varbanov wrote: > This is implementing a multi-stream decoder support. The multi > stream gives an option to use the secondary decoder

Re: [PATCH 26/28] venus: implementing multi-stream support

On 2018-05-02 18:58, Nicolas Dufresne wrote: Le mercredi 02 mai 2018 à 13:10 +0530, Vikash Garodia a écrit : Hello Stanimir, On 2018-04-24 18:14, Stanimir Varbanov wrote: > This is implementing a multi-stream decoder support. The multi > stream gives an option to use the secondary decoder

Re: [PATCH] vhost: make msg padding explicit

From: "Michael S. Tsirkin" Date: Wed, 2 May 2018 16:36:37 +0300 > Ouch. True - and in particular the 32 bit ABI on 64 bit kernels doesn't > work at all. Hmm. It's relatively new and maybe there aren't any 32 bit > users yet. Thoughts? If it's been in a released kernel version,

Re: [PATCH] vhost: make msg padding explicit

From: "Michael S. Tsirkin" Date: Wed, 2 May 2018 16:36:37 +0300 > Ouch. True - and in particular the 32 bit ABI on 64 bit kernels doesn't > work at all. Hmm. It's relatively new and maybe there aren't any 32 bit > users yet. Thoughts? If it's been in a released kernel version, we really aren't

Re: [PATCH v7 2/5] cpuset: Add cpuset.sched_load_balance to v2

On Wed, May 02, 2018 at 09:47:00AM -0400, Waiman Long wrote: > > I've read half of the next patch that adds the isolation thing. And > > while that kludges around the whole root cgorup is magic thing, it > > doesn't help if you move the above scenario on level down: > > > > > > R > > /

Re: [PATCH v7 2/5] cpuset: Add cpuset.sched_load_balance to v2

On Wed, May 02, 2018 at 09:47:00AM -0400, Waiman Long wrote: > > I've read half of the next patch that adds the isolation thing. And > > while that kludges around the whole root cgorup is magic thing, it > > doesn't help if you move the above scenario on level down: > > > > > > R > > /

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

Hi, Peter, Ping again. Did you get chances to think about this issue again? Thanks! Yonghong On 4/27/18 9:34 AM, Yonghong Song wrote: Hi, Peter, Just wanted to ping again so that you did not miss the email below. Please let me know your opinion. Thanks! Yonghong On 4/23/18 9:50 AM,

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

Hi, Peter, Ping again. Did you get chances to think about this issue again? Thanks! Yonghong On 4/27/18 9:34 AM, Yonghong Song wrote: Hi, Peter, Just wanted to ping again so that you did not miss the email below. Please let me know your opinion. Thanks! Yonghong On 4/23/18 9:50 AM,

Re: [PATCH] ALSA: sc6000: fix spelling mistake: "iomaped" -> "iomapped"

On Wed, 02 May 2018 15:59:40 +0200, Colin King wrote: > > From: Colin Ian King > > Trivial fix to spelling mistake in KERN_ERR error messages > > Signed-off-by: Colin Ian King Applied, thanks. Takashi

Re: [PATCH] ALSA: sc6000: fix spelling mistake: "iomaped" -> "iomapped"

On Wed, 02 May 2018 15:59:40 +0200, Colin King wrote: > > From: Colin Ian King > > Trivial fix to spelling mistake in KERN_ERR error messages > > Signed-off-by: Colin Ian King Applied, thanks. Takashi

Re: linux-next: manual merge of the rdma tree with the rdma-fixes tree

On Wed, 2018-05-02 at 13:22 +0300, Leon Romanovsky wrote: > On Mon, Apr 30, 2018 at 08:55:35PM -0400, Doug Ledford wrote: > > On Tue, 2018-05-01 at 10:10 +1000, Stephen Rothwell wrote: > > > Hi all, > > > > > > Today's linux-next merge of the rdma tree got a conflict in: > > > > > >

Re: linux-next: manual merge of the rdma tree with the rdma-fixes tree

On Wed, 2018-05-02 at 13:22 +0300, Leon Romanovsky wrote: > On Mon, Apr 30, 2018 at 08:55:35PM -0400, Doug Ledford wrote: > > On Tue, 2018-05-01 at 10:10 +1000, Stephen Rothwell wrote: > > > Hi all, > > > > > > Today's linux-next merge of the rdma tree got a conflict in: > > > > > >

[tip:irq/urgent] irqchip/qcom: Fix check for spurious interrupts

Commit-ID: 1bc2463cee92ef0e2034c813d5e511adeb58b5fd Gitweb: https://git.kernel.org/tip/1bc2463cee92ef0e2034c813d5e511adeb58b5fd Author: Agustin Vega-Frias AuthorDate: Tue, 1 May 2018 10:14:50 -0400 Committer: Thomas Gleixner CommitDate: Wed,

[tip:irq/urgent] irqchip/qcom: Fix check for spurious interrupts

Commit-ID: 1bc2463cee92ef0e2034c813d5e511adeb58b5fd Gitweb: https://git.kernel.org/tip/1bc2463cee92ef0e2034c813d5e511adeb58b5fd Author: Agustin Vega-Frias AuthorDate: Tue, 1 May 2018 10:14:50 -0400 Committer: Thomas Gleixner CommitDate: Wed, 2 May 2018 15:56:10 +0200 irqchip/qcom: Fix

Re: [RFD] x86: The future of MPX

On Sun, Apr 29, 2018 at 09:44:00PM -0700, Dave Hansen wrote: > The loss of the GCC support is definitely a bummer. https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00027.html Will go into gcc9. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.

Re: [RFD] x86: The future of MPX

On Sun, Apr 29, 2018 at 09:44:00PM -0700, Dave Hansen wrote: > The loss of the GCC support is definitely a bummer. https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00027.html Will go into gcc9. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.

[PATCH] ALSA: sc6000: fix spelling mistake: "iomaped" -> "iomapped"

From: Colin Ian King Trivial fix to spelling mistake in KERN_ERR error messages Signed-off-by: Colin Ian King --- sound/isa/sc6000.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sound/isa/sc6000.c

[PATCH] ALSA: sc6000: fix spelling mistake: "iomaped" -> "iomapped"

From: Colin Ian King Trivial fix to spelling mistake in KERN_ERR error messages Signed-off-by: Colin Ian King --- sound/isa/sc6000.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sound/isa/sc6000.c b/sound/isa/sc6000.c index c09d9b914efe..a985e9183be9 100644 ---

Re: [PATCH] hwtracing: intel_th: Change return type to vm_fault_t

On Wed, May 02, 2018 at 11:14:48AM +0530, Souptick Joarder wrote: > Any comment for this patch ? Looks good, I'm queuing this one for the next merge window. Thanks you!

Re: [PATCH] hwtracing: intel_th: Change return type to vm_fault_t

On Wed, May 02, 2018 at 11:14:48AM +0530, Souptick Joarder wrote: > Any comment for this patch ? Looks good, I'm queuing this one for the next merge window. Thanks you!

Re: [PATCH] clk: stm32mp1: Add CLK_IGNORE_UNUSED to ck_sys_dbg clock

Hi Stephen, This patch is not a critical fix for this merge window. Thanks Gabriel On 05/02/2018 12:10 AM, Stephen Boyd wrote: > Quoting gabriel.fernan...@st.com (2018-04-24 00:58:43) >> From: Gabriel Fernandez >> >> Don't disable the dbg clock if was set by

Re: [PATCH] clk: stm32mp1: Add CLK_IGNORE_UNUSED to ck_sys_dbg clock

Hi Stephen, This patch is not a critical fix for this merge window. Thanks Gabriel On 05/02/2018 12:10 AM, Stephen Boyd wrote: > Quoting gabriel.fernan...@st.com (2018-04-24 00:58:43) >> From: Gabriel Fernandez >> >> Don't disable the dbg clock if was set by bootloader. >> >> Signed-off-by:

[PATCH v2 1/5] x86/mm: surround level4_kernel_pgt with #ifdef CONFIG_X86_5LEVEL...#endif

From: Changbin Du The level4_kernel_pgt is only defined when X86_5LEVEL is enabled. So surround level4_kernel_pgt with #ifdef CONFIG_X86_5LEVEL...#endif to make code correct. Signed-off-by: Changbin Du --- arch/x86/include/asm/pgtable_64.h | 2 ++

[PATCH v2 1/5] x86/mm: surround level4_kernel_pgt with #ifdef CONFIG_X86_5LEVEL...#endif

From: Changbin Du The level4_kernel_pgt is only defined when X86_5LEVEL is enabled. So surround level4_kernel_pgt with #ifdef CONFIG_X86_5LEVEL...#endif to make code correct. Signed-off-by: Changbin Du --- arch/x86/include/asm/pgtable_64.h | 2 ++ arch/x86/kernel/head64.c | 13

[PATCH v2 2/5] regulator: add dummy function of_find_regulator_by_node

From: Changbin Du If device tree is not enabled, of_find_regulator_by_node() should have a dummy function since the function call is still there. This is to fix build error after CONFIG_NO_AUTO_INLINE is introduced. If this option is enabled, GCC will not auto-inline

[PATCH v2 3/5] kernel hacking: new config NO_AUTO_INLINE to disable compiler auto-inline optimizations

From: Changbin Du This patch add a new kernel hacking option NO_AUTO_INLINE. Selecting this option will prevent the compiler from optimizing the kernel by auto-inlining functions not marked with the inline keyword. With this option, only functions explicitly marked with

[PATCH v2 3/5] kernel hacking: new config NO_AUTO_INLINE to disable compiler auto-inline optimizations

From: Changbin Du This patch add a new kernel hacking option NO_AUTO_INLINE. Selecting this option will prevent the compiler from optimizing the kernel by auto-inlining functions not marked with the inline keyword. With this option, only functions explicitly marked with "inline" will be

[PATCH v2 2/5] regulator: add dummy function of_find_regulator_by_node

From: Changbin Du If device tree is not enabled, of_find_regulator_by_node() should have a dummy function since the function call is still there. This is to fix build error after CONFIG_NO_AUTO_INLINE is introduced. If this option is enabled, GCC will not auto-inline functions that are not

Re: [PATCH] gpio: zynq: Setup chip->base based on alias ID

On Wed, May 2, 2018 at 3:41 PM, Michal Simek wrote: > If you don't want this patch I understand that and it will become just > another soc vendor patch out of mainline. I don't really know what to do, so that is why I'm discussing. It's one of those gray areas. >From

Re: [PATCH v2 3/7] clocksource: Initialize cs->wd_list

On Wed, May 02, 2018 at 03:37:30PM +0200, Thomas Gleixner wrote: > On Mon, 30 Apr 2018, Peter Zijlstra wrote: > > > A number of places relies on list_empty(>wd_list), however the > > list_head does not get initialized. Do so upon registration, such that > > thereafter it is possible to rely on

Re: [PATCH] gpio: zynq: Setup chip->base based on alias ID

On Wed, May 2, 2018 at 3:41 PM, Michal Simek wrote: > If you don't want this patch I understand that and it will become just > another soc vendor patch out of mainline. I don't really know what to do, so that is why I'm discussing. It's one of those gray areas. >From one point of view there

Re: [PATCH v2 3/7] clocksource: Initialize cs->wd_list

On Wed, May 02, 2018 at 03:37:30PM +0200, Thomas Gleixner wrote: > On Mon, 30 Apr 2018, Peter Zijlstra wrote: > > > A number of places relies on list_empty(>wd_list), however the > > list_head does not get initialized. Do so upon registration, such that > > thereafter it is possible to rely on

[PATCH v2 4/5] kernel hacking: new config DEBUG_EXPERIENCE to apply GCC -Og optimization

From: Changbin Du This will apply GCC '-Og' optimization level which is supported since GCC 4.8. This optimization level offers a reasonable level of optimization while maintaining fast compilation and a good debugging experience. It is similar to '-O1' while perfer

[PATCH v2 4/5] kernel hacking: new config DEBUG_EXPERIENCE to apply GCC -Og optimization

From: Changbin Du This will apply GCC '-Og' optimization level which is supported since GCC 4.8. This optimization level offers a reasonable level of optimization while maintaining fast compilation and a good debugging experience. It is similar to '-O1' while perfer keeping debug ability over

[PATCH v2 5/5] asm-generic: fix build error in fix_to_virt with CONFIG_DEBUG_EXPERIENCE

From: Changbin Du With '-Og' optimization level, GCC would not optimize a count for a loop as a constant value. But BUILD_BUG_ON() only accept compile-time constant values. arch/arm/mm/mmu.o: In function `fix_to_virt':

[PATCH v2 5/5] asm-generic: fix build error in fix_to_virt with CONFIG_DEBUG_EXPERIENCE

From: Changbin Du With '-Og' optimization level, GCC would not optimize a count for a loop as a constant value. But BUILD_BUG_ON() only accept compile-time constant values. arch/arm/mm/mmu.o: In function `fix_to_virt': /home/changbin/work/linux/./include/asm-generic/fixmap.h:31: undefined

[PATCH v2 0/5] kernel hacking: GCC optimization for debug experience (-Og)

From: Changbin Du Hi all, I know some kernel developers was searching for a method to dissable GCC optimizations, probably they want to apply GCC '-O0' option. But since Linux kernel replys on GCC optimization to remove some dead code, so '-O0' just breaks the build. They

[PATCH v2 0/5] kernel hacking: GCC optimization for debug experience (-Og)

From: Changbin Du Hi all, I know some kernel developers was searching for a method to dissable GCC optimizations, probably they want to apply GCC '-O0' option. But since Linux kernel replys on GCC optimization to remove some dead code, so '-O0' just breaks the build. They do need this because

Re: [RFC PATCH RESEND 2/3] leds: upboard: Add LED support

On Thu, 2018-04-26 at 13:49 +0100, Javier Arteaga wrote: > On Thu, Apr 26, 2018 at 10:55:49AM +0300, Andy Shevchenko wrote: > > On Thu, 2018-04-26 at 03:34 +0100, Javier Arteaga wrote: > > > My understanding was that in this context, __init allows this > > > probe() > > > to > > > be dropped from

Re: [RFC PATCH RESEND 2/3] leds: upboard: Add LED support

On Thu, 2018-04-26 at 13:49 +0100, Javier Arteaga wrote: > On Thu, Apr 26, 2018 at 10:55:49AM +0300, Andy Shevchenko wrote: > > On Thu, 2018-04-26 at 03:34 +0100, Javier Arteaga wrote: > > > My understanding was that in this context, __init allows this > > > probe() > > > to > > > be dropped from

Re: [PATCH v2 2/7] clocksource: Allow clocksource_mark_unstable() on unregisered clocksources

On Wed, May 02, 2018 at 03:35:53PM +0200, Thomas Gleixner wrote: > On Mon, 30 Apr 2018, Peter Zijlstra wrote: > > --- a/kernel/time/clocksource.c > > +++ b/kernel/time/clocksource.c > > @@ -119,6 +119,16 @@ static DEFINE_SPINLOCK(watchdog_lock); > > static int watchdog_running; > > static

Re: [PATCH v2 2/7] clocksource: Allow clocksource_mark_unstable() on unregisered clocksources

On Wed, May 02, 2018 at 03:35:53PM +0200, Thomas Gleixner wrote: > On Mon, 30 Apr 2018, Peter Zijlstra wrote: > > --- a/kernel/time/clocksource.c > > +++ b/kernel/time/clocksource.c > > @@ -119,6 +119,16 @@ static DEFINE_SPINLOCK(watchdog_lock); > > static int watchdog_running; > > static

Re: [PATCH v2 21/27] coresight: Convert driver messages to dev_dbg

On 02/05/18 04:55, Kim Phillips wrote: On Tue, 1 May 2018 10:10:51 +0100 Suzuki K Poulose wrote: Convert component enable/disable messages from dev_info to dev_dbg. This is required to prevent LOCKDEP splats when operating in perf mode where we could be called with

Re: [PATCH v2 21/27] coresight: Convert driver messages to dev_dbg

On 02/05/18 04:55, Kim Phillips wrote: On Tue, 1 May 2018 10:10:51 +0100 Suzuki K Poulose wrote: Convert component enable/disable messages from dev_info to dev_dbg. This is required to prevent LOCKDEP splats when operating in perf mode where we could be called with locks held to enable a

Re: [PATCH 0/6] use memcpy_mcsafe() for copy_to_iter()

On Wed, May 2, 2018 at 1:30 AM, Borislav Petkov wrote: > On Tue, May 01, 2018 at 07:25:57PM -0700, Dan Williams wrote: >> Right, but the only way to make MCE non-fatal is to teach the machine >> check handler about recoverable conditions. This patch teaches the >> machine check

Re: [PATCH 0/6] use memcpy_mcsafe() for copy_to_iter()

On Wed, May 2, 2018 at 1:30 AM, Borislav Petkov wrote: > On Tue, May 01, 2018 at 07:25:57PM -0700, Dan Williams wrote: >> Right, but the only way to make MCE non-fatal is to teach the machine >> check handler about recoverable conditions. This patch teaches the >> machine check handler how to

<    8   9   10   11   12   13   14   15   16   17   >