Re: [PATCH v2] Linux VM workaround for Knights Landing A/D leak

On 06/14/16 13:47, Borislav Petkov wrote: > On Tue, Jun 14, 2016 at 01:20:06PM -0700, H. Peter Anvin wrote: >> static_cpu_has_bug() should turn into 5-byte NOP in the common (bugless) >> case. > > Yeah, it does. I looked at the asm. > > I wasn't 100% sure because I vaguely remember gcc

Re: [PATCH v2] Linux VM workaround for Knights Landing A/D leak

On 06/14/16 13:47, Borislav Petkov wrote: > On Tue, Jun 14, 2016 at 01:20:06PM -0700, H. Peter Anvin wrote: >> static_cpu_has_bug() should turn into 5-byte NOP in the common (bugless) >> case. > > Yeah, it does. I looked at the asm. > > I wasn't 100% sure because I vaguely remember gcc

Re: [PATCH] Add kernel parameter to blacklist modules

On Tue, 14 Jun 2016, Christoph Hellwig wrote: > On Mon, Jun 13, 2016 at 08:32:41AM -0400, Prarit Bhargava wrote: > > Blacklisting a module in linux has long been a problem. The process of > > blacklisting a module has changed over time, and it seems that every OS > > does it slightly differently

Re: [PATCH] Add kernel parameter to blacklist modules

On Tue, 14 Jun 2016, Christoph Hellwig wrote: > On Mon, Jun 13, 2016 at 08:32:41AM -0400, Prarit Bhargava wrote: > > Blacklisting a module in linux has long been a problem. The process of > > blacklisting a module has changed over time, and it seems that every OS > > does it slightly differently

[PATCH 4/7] liblockdep: Enable -Wall by default

Regressions in liblockdep may be missed because it doesn't enable warnings. Adding -Wall immediately introduces a lot of warnings, but those will be fixed by the following commits. Signed-off-by: Ben Hutchings --- tools/lib/lockdep/Makefile | 1 + 1 file changed, 1

[PATCH 4/7] liblockdep: Enable -Wall by default

Regressions in liblockdep may be missed because it doesn't enable warnings. Adding -Wall immediately introduces a lot of warnings, but those will be fixed by the following commits. Signed-off-by: Ben Hutchings --- tools/lib/lockdep/Makefile | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH 5/7] liblockdep: Fix 'unused value' warnings

liblockdep defines various macros that may expand to an expression with no effect, while the in-kernel definition does have an effect. This results in warnings from gcc when -Wunused-value is enabled, and is is enabled by -Wall. Fix this by introducing trivial functions, as function return values

[PATCH 7/7] liblockdep: Fix 'defined but not used' warning for init_utsname()

We define init_utsname() as static but not inline, resulting in a warning for every source file that includes lockdep.h but doesn't call it. Since it is only used by lockdep.c, define it in there. Signed-off-by: Ben Hutchings --- tools/lib/lockdep/lockdep.c

[PATCH 5/7] liblockdep: Fix 'unused value' warnings

liblockdep defines various macros that may expand to an expression with no effect, while the in-kernel definition does have an effect. This results in warnings from gcc when -Wunused-value is enabled, and is is enabled by -Wall. Fix this by introducing trivial functions, as function return values

[PATCH 7/7] liblockdep: Fix 'defined but not used' warning for init_utsname()

We define init_utsname() as static but not inline, resulting in a warning for every source file that includes lockdep.h but doesn't call it. Since it is only used by lockdep.c, define it in there. Signed-off-by: Ben Hutchings --- tools/lib/lockdep/lockdep.c| 10 ++

[PATCH 6/7] liblockdep: Fix 'set but not used' warnings

liblockdep defines trivial macros for working with interrupt flags, as interrupts are never disabled in userland. This results in warnings from gcc when -Wunused-but-set-variable is enabled, and it is enabled by -Wall. Fix this by evaluating the flags parameter and casting it to void.

[PATCH 6/7] liblockdep: Fix 'set but not used' warnings

liblockdep defines trivial macros for working with interrupt flags, as interrupts are never disabled in userland. This results in warnings from gcc when -Wunused-but-set-variable is enabled, and it is enabled by -Wall. Fix this by evaluating the flags parameter and casting it to void.

[PATCH 3/7] liblockdep: Define the ARRAY_SIZE() macro

lockdep.c now uses ARRAY_SIZE(). Fixes: 75dd602a5198 ("lockdep: Fix lock_chain::base size") Signed-off-by: Ben Hutchings --- tools/lib/lockdep/uinclude/linux/kernel.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/lib/lockdep/uinclude/linux/kernel.h

[PATCH 3/7] liblockdep: Define the ARRAY_SIZE() macro

lockdep.c now uses ARRAY_SIZE(). Fixes: 75dd602a5198 ("lockdep: Fix lock_chain::base size") Signed-off-by: Ben Hutchings --- tools/lib/lockdep/uinclude/linux/kernel.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/lib/lockdep/uinclude/linux/kernel.h

Re: [PATCH v2] Linux VM workaround for Knights Landing A/D leak

On Tue, Jun 14, 2016 at 01:20:06PM -0700, H. Peter Anvin wrote: > static_cpu_has_bug() should turn into 5-byte NOP in the common (bugless) > case. Yeah, it does. I looked at the asm. I wasn't 100% sure because I vaguely remember gcc reordering things in some pathological case but I'm most likely

Re: [PATCH v2] Linux VM workaround for Knights Landing A/D leak

On Tue, Jun 14, 2016 at 01:20:06PM -0700, H. Peter Anvin wrote: > static_cpu_has_bug() should turn into 5-byte NOP in the common (bugless) > case. Yeah, it does. I looked at the asm. I wasn't 100% sure because I vaguely remember gcc reordering things in some pathological case but I'm most likely

Re: [PATCH 4/4] coccicheck: add indexing enhancement options

On Tue, 14 Jun 2016, Luis R. Rodriguez wrote: > On Tue, Jun 14, 2016 at 07:22:03AM +0200, Julia Lawall wrote: > > > > > > On Mon, 13 Jun 2016, Luis R. Rodriguez wrote: > > > > > On Mon, Jun 13, 2016 at 09:50:15PM +0200, Julia Lawall wrote: > > > > > > > > > > > > On Mon, 13 Jun 2016, Luis

[PATCH 2/7] liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing lock_chain::depth

liblockdep has been broken since commit 75dd602a5198 ("lockdep: Fix lock_chain::base size"), as that adds a check that MAX_LOCK_DEPTH is within the range of lock_chain::depth and in liblockdep it is much too large. That should have resulted in a compiler error, but didn't because: - the check

Re: [PATCH 4/4] coccicheck: add indexing enhancement options

On Tue, 14 Jun 2016, Luis R. Rodriguez wrote: > On Tue, Jun 14, 2016 at 07:22:03AM +0200, Julia Lawall wrote: > > > > > > On Mon, 13 Jun 2016, Luis R. Rodriguez wrote: > > > > > On Mon, Jun 13, 2016 at 09:50:15PM +0200, Julia Lawall wrote: > > > > > > > > > > > > On Mon, 13 Jun 2016, Luis

[PATCH 2/7] liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing lock_chain::depth

liblockdep has been broken since commit 75dd602a5198 ("lockdep: Fix lock_chain::base size"), as that adds a check that MAX_LOCK_DEPTH is within the range of lock_chain::depth and in liblockdep it is much too large. That should have resulted in a compiler error, but didn't because: - the check

[PATCH 1/7] liblockdep: Fix undefined symbol prandom_u32

__lock_pin_lock() now calls prandom_u32() which is not defined in liblockdep. __lock_pin_lock() and its caller lock_pin_lock() are dead code in liblockdep, but we still need to provide a definition of prandom_u32() in case lazy binding is disabled. Fixes: e7904a28f533 ("locking/lockdep,

[PATCH 1/7] liblockdep: Fix undefined symbol prandom_u32

__lock_pin_lock() now calls prandom_u32() which is not defined in liblockdep. __lock_pin_lock() and its caller lock_pin_lock() are dead code in liblockdep, but we still need to provide a definition of prandom_u32() in case lazy binding is disabled. Fixes: e7904a28f533 ("locking/lockdep,

Re: [PATCH] mdio: mux: avoid 'maybe-uninitialized' warning

On Tue, Jun 14, 2016 at 12:03:17PM +0200, Arnd Bergmann wrote: > The latest changes to the MDIO code introduced a false-positive > warning with gcc-6 (possibly others): > > drivers/net/phy/mdio-mux.c: In function 'mdio_mux_init': > drivers/net/phy/mdio-mux.c:188:3: error: 'parent_bus_node' may be

Re: [PATCH] mdio: mux: avoid 'maybe-uninitialized' warning

On Tue, Jun 14, 2016 at 12:03:17PM +0200, Arnd Bergmann wrote: > The latest changes to the MDIO code introduced a false-positive > warning with gcc-6 (possibly others): > > drivers/net/phy/mdio-mux.c: In function 'mdio_mux_init': > drivers/net/phy/mdio-mux.c:188:3: error: 'parent_bus_node' may be

[PATCH 0/7] Fixes for liblockdep

Here are a number of fixes for liblockdep. The first three need to go into 4.7 and 4.6-stable; the second should probably go to all stable branches. Ben. Ben Hutchings (7): liblockdep: Fix undefined symbol prandom_u32 liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing

[PATCH 0/7] Fixes for liblockdep

Here are a number of fixes for liblockdep. The first three need to go into 4.7 and 4.6-stable; the second should probably go to all stable branches. Ben. Ben Hutchings (7): liblockdep: Fix undefined symbol prandom_u32 liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing

Re: [PATCH 0/10 -v4] Handle oom bypass more gracefully

On 06/14, Oleg Nesterov wrote: > > So to me this additional patch looks fine, forgot to mention, but I think it needs another change in task_will_free_mem(), it should ignore kthreads (should not fail if we see a kthread which shares task->mm). And the comment you added on top of use_mm() looks

Re: [PATCH 0/10 -v4] Handle oom bypass more gracefully

On 06/14, Oleg Nesterov wrote: > > So to me this additional patch looks fine, forgot to mention, but I think it needs another change in task_will_free_mem(), it should ignore kthreads (should not fail if we see a kthread which shares task->mm). And the comment you added on top of use_mm() looks

Re: [patch 13/20] timer: Switch to a non cascading wheel

On Tue, Jun 14, 2016 at 08:05:49PM +0200, Thomas Gleixner wrote: > On Tue, 14 Jun 2016, Arjan van de Ven wrote: > > > evaluating a 120 hours timer ever 37 hours to see if it should fire... > > not too horrid. > > Well that thing is doing weird stuff anyway: > >swapper 0 [001]

Re: [patch 13/20] timer: Switch to a non cascading wheel

On Tue, Jun 14, 2016 at 08:05:49PM +0200, Thomas Gleixner wrote: > On Tue, 14 Jun 2016, Arjan van de Ven wrote: > > > evaluating a 120 hours timer ever 37 hours to see if it should fire... > > not too horrid. > > Well that thing is doing weird stuff anyway: > >swapper 0 [001]

Re: [PATCH 1/1] kernel/sysctl.c: avoid overflow

On Tue, Jun 14, 2016 at 01:19:06PM -0700, Andrew Morton wrote: > On Sat, 11 Jun 2016 03:33:08 +0200 Heinrich Schuchardt > wrote: > > > An undetected overflow may occur in do_proc_dointvec_minmax_conv_param. > > > > ... > > > > --- a/kernel/sysctl.c > > +++ b/kernel/sysctl.c

Re: [PATCH 1/1] kernel/sysctl.c: avoid overflow

On Tue, Jun 14, 2016 at 01:19:06PM -0700, Andrew Morton wrote: > On Sat, 11 Jun 2016 03:33:08 +0200 Heinrich Schuchardt > wrote: > > > An undetected overflow may occur in do_proc_dointvec_minmax_conv_param. > > > > ... > > > > --- a/kernel/sysctl.c > > +++ b/kernel/sysctl.c > > @@ -2313,7

Re: [very-RFC 0/8] TSN driver for the kernel

On Tue, Jun 14, 2016 at 08:26:15PM +0200, Richard Cochran wrote: > On Tue, Jun 14, 2016 at 11:30:00AM +0200, Henrik Austad wrote: > > So loop data from kernel -> userspace -> kernelspace and finally back to > > userspace and the media application? > > Huh? I wonder where you got that idea. Let

Re: [very-RFC 0/8] TSN driver for the kernel

On Tue, Jun 14, 2016 at 08:26:15PM +0200, Richard Cochran wrote: > On Tue, Jun 14, 2016 at 11:30:00AM +0200, Henrik Austad wrote: > > So loop data from kernel -> userspace -> kernelspace and finally back to > > userspace and the media application? > > Huh? I wonder where you got that idea. Let

Re: [PATCH V6] irq: Track the interrupt timings

On Tue, 14 Jun 2016, Daniel Lezcano wrote: > The interrupt framework gives a lot of information about each interrupt. > > It does not keep track of when those interrupts occur though. > > This patch provides a mean to record the elapsed time between successive > interrupt occurrences in a

Re: [PATCH V6] irq: Track the interrupt timings

On Tue, 14 Jun 2016, Daniel Lezcano wrote: > The interrupt framework gives a lot of information about each interrupt. > > It does not keep track of when those interrupts occur though. > > This patch provides a mean to record the elapsed time between successive > interrupt occurrences in a

Re: [patch 13/20] timer: Switch to a non cascading wheel

On Tue, Jun 14, 2016 at 08:05:49PM +0200, Thomas Gleixner wrote: > On Tue, 14 Jun 2016, Arjan van de Ven wrote: > > > evaluating a 120 hours timer ever 37 hours to see if it should fire... > > not too horrid. > > Well that thing is doing weird stuff anyway: > >swapper 0 [001]

Re: [patch 13/20] timer: Switch to a non cascading wheel

On Tue, Jun 14, 2016 at 08:05:49PM +0200, Thomas Gleixner wrote: > On Tue, 14 Jun 2016, Arjan van de Ven wrote: > > > evaluating a 120 hours timer ever 37 hours to see if it should fire... > > not too horrid. > > Well that thing is doing weird stuff anyway: > >swapper 0 [001]

Re: [PATCH 2/4] mtd: nand: implement two pairing scheme

On 14 Jun 2016 05:07:26 -0400 "George Spelvin" wrote: > Boris Brezillon wrote: > > On 12 Jun 2016 16:24:53 George Spelvin wrote: > >> Boris Brezillon wrote: > >> My problem is that I don't really understand MLC programming. > > > I came to the same conclusion: we

Re: [PATCH 2/4] mtd: nand: implement two pairing scheme

On 14 Jun 2016 05:07:26 -0400 "George Spelvin" wrote: > Boris Brezillon wrote: > > On 12 Jun 2016 16:24:53 George Spelvin wrote: > >> Boris Brezillon wrote: > >> My problem is that I don't really understand MLC programming. > > > I came to the same conclusion: we really have these 2 cases

Re: [RFC][PATCH 2/8] sched/rtmutex/deadline: Fix a PI crash for deadline tasks

On Tue, Jun 14, 2016 at 02:42:17PM -0400, Steven Rostedt wrote: > On Tue, 07 Jun 2016 21:56:37 +0200 > Peter Zijlstra wrote: > > + /* > > +* We should deboost before waking the top waiter task such that > > +* we don't run two tasks with the 'same' priority. This

Re: [RFC][PATCH 2/8] sched/rtmutex/deadline: Fix a PI crash for deadline tasks

On Tue, Jun 14, 2016 at 02:42:17PM -0400, Steven Rostedt wrote: > On Tue, 07 Jun 2016 21:56:37 +0200 > Peter Zijlstra wrote: > > + /* > > +* We should deboost before waking the top waiter task such that > > +* we don't run two tasks with the 'same' priority. This however > > +* can

[PATCH] i2c: tegra: Correct error path in probe

Commit 497fbe24987b ("i2c: tegra: enable multi master mode for tegra210") enables the Tegra I2C 'div_clk' for adapters using the multi-master mode during the device probe. Although the probe error path was updated to disable the clock on probe failure, there is one place after calling

[PATCH] i2c: tegra: Correct error path in probe

Commit 497fbe24987b ("i2c: tegra: enable multi master mode for tegra210") enables the Tegra I2C 'div_clk' for adapters using the multi-master mode during the device probe. Although the probe error path was updated to disable the clock on probe failure, there is one place after calling

[PATCH v3 1/6] coccicheck: move spatch binary check up

This has no functional changes. This is being done to enable us to later use spatch binary for some flag checking for certain features early on. Signed-off-by: Luis R. Rodriguez --- scripts/coccicheck | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff

[PATCH v3 2/6] coccicheck: enable parmap support

Coccinelle has had parmap support since 1.0.2, this means it supports --jobs, enabling built-in multithreaded functionality, instead of needing one to script it out. Just look for --jobs in the help output to determine if this is supported. Also enable the load balancing to be dynamic, so that if

[PATCH v3 1/6] coccicheck: move spatch binary check up

This has no functional changes. This is being done to enable us to later use spatch binary for some flag checking for certain features early on. Signed-off-by: Luis R. Rodriguez --- scripts/coccicheck | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH v3 2/6] coccicheck: enable parmap support

Coccinelle has had parmap support since 1.0.2, this means it supports --jobs, enabling built-in multithreaded functionality, instead of needing one to script it out. Just look for --jobs in the help output to determine if this is supported. Also enable the load balancing to be dynamic, so that if

[PATCH v3 0/6] coccicheck: extend with parmap and indexing heuristics

I fat fingered the v2 series and forgot the first patch, this just adds the first patch... sorry about that. Luis R. Rodriguez (6): coccicheck: move spatch binary check up coccicheck: enable parmap support scripts: add glimpse.sh for indexing the kernel coccicheck: add indexing

[PATCH v3 4/6] coccicheck: add indexing enhancement options

Coccinelle has support to make use of its own enhanced "grep" mechanisms instead of using regular grep for searching code, it calls this 'coccigrep'. In lack of any indexing optimization information it uses --use-coccigrep by default. This patch enable indexing optimizations heuristics so that

[PATCH v3 0/6] coccicheck: extend with parmap and indexing heuristics

I fat fingered the v2 series and forgot the first patch, this just adds the first patch... sorry about that. Luis R. Rodriguez (6): coccicheck: move spatch binary check up coccicheck: enable parmap support scripts: add glimpse.sh for indexing the kernel coccicheck: add indexing

[PATCH v3 4/6] coccicheck: add indexing enhancement options

Coccinelle has support to make use of its own enhanced "grep" mechanisms instead of using regular grep for searching code, it calls this 'coccigrep'. In lack of any indexing optimization information it uses --use-coccigrep by default. This patch enable indexing optimizations heuristics so that

[PATCH v3 5/6] coccicheck: document how to pass extra options to coccinelle

As an example show how to debug your coccinelle script. While at it, fix the case when --profile is passed, when --profile is used we need to ensure --very-quiet is not used. For instance one can use: $ export COCCI=scripts/coccinelle/misc/irqf_oneshot.cocci $ make coccicheck MODE=report

[PATCH v3 5/6] coccicheck: document how to pass extra options to coccinelle

As an example show how to debug your coccinelle script. While at it, fix the case when --profile is passed, when --profile is used we need to ensure --very-quiet is not used. For instance one can use: $ export COCCI=scripts/coccinelle/misc/irqf_oneshot.cocci $ make coccicheck MODE=report

[PATCH v3 6/6] coccicheck: refer to coccicheck bottest wiki for documentation

Sprinkling *tons* of documentation on the script is not a good idea, instead refer to a wiki for further coccicheck documentation: https://bottest.wiki.kernel.org/coccicheck This page shall always refer to the linux-next iteration of scripts/coccicheck. Signed-off-by: Luis R. Rodriguez

[PATCH v3 3/6] scripts: add glimpse.sh for indexing the kernel

Glimpse is a tool you can use to index the kernel. The tool was recently open sourced under the ISC license and can be obtained at: https://github.com/mcgrof/glimpse.git Signed-off-by: Luis R. Rodriguez --- scripts/glimpse.sh | 12 1 file changed, 12

[PATCH v3 6/6] coccicheck: refer to coccicheck bottest wiki for documentation

Sprinkling *tons* of documentation on the script is not a good idea, instead refer to a wiki for further coccicheck documentation: https://bottest.wiki.kernel.org/coccicheck This page shall always refer to the linux-next iteration of scripts/coccicheck. Signed-off-by: Luis R. Rodriguez ---

[PATCH v3 3/6] scripts: add glimpse.sh for indexing the kernel

Glimpse is a tool you can use to index the kernel. The tool was recently open sourced under the ISC license and can be obtained at: https://github.com/mcgrof/glimpse.git Signed-off-by: Luis R. Rodriguez --- scripts/glimpse.sh | 12 1 file changed, 12 insertions(+) create mode

Re: [PATCH v2 00/13] Runtime PM for Thunderbolt on Macs

On Tue, Jun 14, 2016 at 09:14:27PM +0200, Andreas Noever wrote: > On Tue, Jun 14, 2016 at 6:37 PM, Bjorn Helgaas wrote: > > [+cc linux-kernel] > > > > On Sat, May 21, 2016 at 11:48:42AM +0200, Andreas Noever wrote: > >> > >> Signed-off-by: Andreas Noever

[PATCH] arm64: dts: rockchip: add ap_pwroff and ddrio_pwroff pins for rk3399

There are two sleep related pins on rk3399: ap_pwroff and ddrio_pwroff. Let's add the definition of these two pins to rk3399's main dtsi file so that boards can use them. These two pins are similar to the global_pwroff and ddrio_pwroff pins in rk3288 and are expected to be used in the same way:

Re: [PATCH v2 00/13] Runtime PM for Thunderbolt on Macs

On Tue, Jun 14, 2016 at 09:14:27PM +0200, Andreas Noever wrote: > On Tue, Jun 14, 2016 at 6:37 PM, Bjorn Helgaas wrote: > > [+cc linux-kernel] > > > > On Sat, May 21, 2016 at 11:48:42AM +0200, Andreas Noever wrote: > >> > >> Signed-off-by: Andreas Noever > >> > >> Tested on MacBookPro10,1 > >> >

[PATCH] arm64: dts: rockchip: add ap_pwroff and ddrio_pwroff pins for rk3399

There are two sleep related pins on rk3399: ap_pwroff and ddrio_pwroff. Let's add the definition of these two pins to rk3399's main dtsi file so that boards can use them. These two pins are similar to the global_pwroff and ddrio_pwroff pins in rk3288 and are expected to be used in the same way:

Re: [PATCH net-next v4 0/7] vmxnet3: upgrade to version 3

On 06/14/2016 11:52 AM, Shrikrishna Khare wrote: > This patchset upgrades vmxnet3 to version 3. > > Changes in v2: > - Following patch is updated. See that patch for details: >vmxnet3: add support for get_coalesce, set_coalesce ethtool > > Changes in v3: > - fix subject line to use

Re: [PATCH net-next v4 0/7] vmxnet3: upgrade to version 3

On 06/14/2016 11:52 AM, Shrikrishna Khare wrote: > This patchset upgrades vmxnet3 to version 3. > > Changes in v2: > - Following patch is updated. See that patch for details: >vmxnet3: add support for get_coalesce, set_coalesce ethtool > > Changes in v3: > - fix subject line to use

Re: [PATCH v2] Linux VM workaround for Knights Landing A/D leak

On 06/14/16 12:19, Borislav Petkov wrote: > On Tue, Jun 14, 2016 at 11:54:24AM -0700, Dave Hansen wrote: >> Lukasz, Borislav suggested using static_cpu_has_bug(), which will do the >> alternatives patching. It's definitely the right thing to use here. > > Yeah, either that or do an > >

Re: [PATCH v2] Linux VM workaround for Knights Landing A/D leak

On 06/14/16 12:19, Borislav Petkov wrote: > On Tue, Jun 14, 2016 at 11:54:24AM -0700, Dave Hansen wrote: >> Lukasz, Borislav suggested using static_cpu_has_bug(), which will do the >> alternatives patching. It's definitely the right thing to use here. > > Yeah, either that or do an > >

[4.2.y-ckt stable] Linux 4.2.8-ckt12

I am announcing the release of the Linux 4.2.8-ckt12 kernel. The updated 4.2.y-ckt tree can be found at: git://git.launchpad.net/~canonical-kernel/linux/+git/linux-stable-ckt linux-4.2.y and can be browsed at:

[4.2.y-ckt stable] Linux 4.2.8-ckt12

I am announcing the release of the Linux 4.2.8-ckt12 kernel. The updated 4.2.y-ckt tree can be found at: git://git.launchpad.net/~canonical-kernel/linux/+git/linux-stable-ckt linux-4.2.y and can be browsed at:

Re: [PATCH v3 3/3] LSM: Add context interface for proc attr

On 6/14/2016 11:57 AM, Kees Cook wrote: > On Fri, Jun 10, 2016 at 2:25 PM, Casey Schaufler > wrote: >> Subject: [PATCH v3 3/3] LSM: Add context interface for proc attrs >> >> The /proc/.../attr/current interface is used by all three >> Linux security modules (SELinux,

Re: [PATCH v3 3/3] LSM: Add context interface for proc attr

On 6/14/2016 11:57 AM, Kees Cook wrote: > On Fri, Jun 10, 2016 at 2:25 PM, Casey Schaufler > wrote: >> Subject: [PATCH v3 3/3] LSM: Add context interface for proc attrs >> >> The /proc/.../attr/current interface is used by all three >> Linux security modules (SELinux, Smack and AppArmor) to >>

Re: [PATCH 0/6] Support DAX for device-mapper dm-linear devices

Mike Snitzer writes: > On Tue, Jun 14 2016 at 9:50am -0400, > Jeff Moyer wrote: > >> "Kani, Toshimitsu" writes: >> >> >> I had dm-linear and md-raid0 support on my list of things to look at, >> >> did you have raid0 in your plans? >>

Re: [PATCH 0/6] Support DAX for device-mapper dm-linear devices

Mike Snitzer writes: > On Tue, Jun 14 2016 at 9:50am -0400, > Jeff Moyer wrote: > >> "Kani, Toshimitsu" writes: >> >> >> I had dm-linear and md-raid0 support on my list of things to look at, >> >> did you have raid0 in your plans? >> > >> > Yes, I hope to extend further and raid0 is a good

Re: [PATCH 1/1] kernel/sysctl.c: avoid overflow

On Sat, 11 Jun 2016 03:33:08 +0200 Heinrich Schuchardt wrote: > An undetected overflow may occur in do_proc_dointvec_minmax_conv_param. > > ... > > --- a/kernel/sysctl.c > +++ b/kernel/sysctl.c > @@ -2313,7 +2313,17 @@ static int do_proc_dointvec_minmax_conv(bool *negp, >

Re: [PATCH v2 0/5] coccicheck: extend with parmap and indexing heuristics

On Tue, Jun 14, 2016 at 01:05:47PM -0700, Luis R. Rodriguez wrote: > This v2 addresses the feedback from the v1 series. It also adds 2 more > patches, one to document how to add extra additional options and refers > to a wiki for further documentation. > > Luis R. Rodriguez (5): > coccicheck:

Re: [PATCH 1/1] kernel/sysctl.c: avoid overflow

On Sat, 11 Jun 2016 03:33:08 +0200 Heinrich Schuchardt wrote: > An undetected overflow may occur in do_proc_dointvec_minmax_conv_param. > > ... > > --- a/kernel/sysctl.c > +++ b/kernel/sysctl.c > @@ -2313,7 +2313,17 @@ static int do_proc_dointvec_minmax_conv(bool *negp, > unsigned long

Re: [PATCH v2 0/5] coccicheck: extend with parmap and indexing heuristics

On Tue, Jun 14, 2016 at 01:05:47PM -0700, Luis R. Rodriguez wrote: > This v2 addresses the feedback from the v1 series. It also adds 2 more > patches, one to document how to add extra additional options and refers > to a wiki for further documentation. > > Luis R. Rodriguez (5): > coccicheck:

[PATCH] [media] v4l2-ioctl.c: fix warning due wrong check in v4l_cropcap()

Commit 95dd7b7e30f3 ("[media] v4l2-ioctl.c: improve cropcap compatibility code") tried to check if both .vidioc_cropcap and .vidioc_g_selection are NULL ops and warn if that was the case, but unfortunately the logic isn't correct and instead checks for .vidioc_cropcap == NULL twice. So the v4l2

[PATCH] [media] v4l2-ioctl.c: fix warning due wrong check in v4l_cropcap()

Commit 95dd7b7e30f3 ("[media] v4l2-ioctl.c: improve cropcap compatibility code") tried to check if both .vidioc_cropcap and .vidioc_g_selection are NULL ops and warn if that was the case, but unfortunately the logic isn't correct and instead checks for .vidioc_cropcap == NULL twice. So the v4l2

Re: [PATCH 0/10 -v4] Handle oom bypass more gracefully

On 06/13, Michal Hocko wrote: > > On Mon 13-06-16 13:23:48, Michal Hocko wrote: > > On Thu 09-06-16 13:52:07, Michal Hocko wrote: > > > I would like to explore ways how to remove kthreads (use_mm) special > > > case. It shouldn't be that hard, we just have to teach the page fault > > > handler to

Re: [PATCH 0/10 -v4] Handle oom bypass more gracefully

On 06/13, Michal Hocko wrote: > > On Mon 13-06-16 13:23:48, Michal Hocko wrote: > > On Thu 09-06-16 13:52:07, Michal Hocko wrote: > > > I would like to explore ways how to remove kthreads (use_mm) special > > > case. It shouldn't be that hard, we just have to teach the page fault > > > handler to

Re: [PATCH] Linux VM workaround for Knights Landing A/D leak

Dave Hansen wrote: > On 06/14/2016 09:47 AM, Nadav Amit wrote: >> Lukasz Anaczkowski wrote: >> From: Andi Kleen +void fix_pte_leak(struct mm_struct *mm, unsigned long addr, pte_t *ptep) +{ >> Here

Re: [PATCH] Linux VM workaround for Knights Landing A/D leak

Dave Hansen wrote: > On 06/14/2016 09:47 AM, Nadav Amit wrote: >> Lukasz Anaczkowski wrote: >> From: Andi Kleen +void fix_pte_leak(struct mm_struct *mm, unsigned long addr, pte_t *ptep) +{ >> Here there should be a call to smp_mb__after_atomic() to synchronize with >>

[PATCH V6] irq: Track the interrupt timings

The interrupt framework gives a lot of information about each interrupt. It does not keep track of when those interrupts occur though. This patch provides a mean to record the elapsed time between successive interrupt occurrences in a per-IRQ per-CPU circular buffer to help with the prediction

[PATCH V6] irq: Track the interrupt timings

The interrupt framework gives a lot of information about each interrupt. It does not keep track of when those interrupts occur though. This patch provides a mean to record the elapsed time between successive interrupt occurrences in a per-IRQ per-CPU circular buffer to help with the prediction

Re: [PATCH v2] backlight: lp855x: Add enable regulator

On Fri, Jun 10, 2016 at 12:39:57PM -0700, Brian Norris wrote: > The LP8556 datasheet describes an EN/VDDIO input, which serves "both as > a chip enable and as a power supply reference for PWM, SDA, and SCL > inputs." The LP8556 that I'm testing doesn't respond properly if I try > to talk I2C to it

Re: [PATCH v2] backlight: lp855x: Add enable regulator

On Fri, Jun 10, 2016 at 12:39:57PM -0700, Brian Norris wrote: > The LP8556 datasheet describes an EN/VDDIO input, which serves "both as > a chip enable and as a power supply reference for PWM, SDA, and SCL > inputs." The LP8556 that I'm testing doesn't respond properly if I try > to talk I2C to it

[PATCH v2 5/5] coccicheck: refer to coccicheck bottest wiki for documentation

Sprinkling *tons* of documentation on the script is not a good idea, instead refer to a wiki for further coccicheck documentation: https://bottest.wiki.kernel.org/coccicheck This page shall always refer to the linux-next iteration of scripts/coccicheck. Signed-off-by: Luis R. Rodriguez

[PATCH v2 0/5] coccicheck: extend with parmap and indexing heuristics

This v2 addresses the feedback from the v1 series. It also adds 2 more patches, one to document how to add extra additional options and refers to a wiki for further documentation. Luis R. Rodriguez (5): coccicheck: enable parmap support scripts: add glimpse.sh for indexing the kernel

[PATCH v2 4/5] coccicheck: document how to pass extra options to coccinelle

As an example show how to debug your coccinelle script. While at it, fix the case when --profile is passed, when --profile is used we need to ensure --very-quiet is not used. For instance one can use: $ export COCCI=scripts/coccinelle/misc/irqf_oneshot.cocci $ make coccicheck MODE=report

[PATCH v2 5/5] coccicheck: refer to coccicheck bottest wiki for documentation

Sprinkling *tons* of documentation on the script is not a good idea, instead refer to a wiki for further coccicheck documentation: https://bottest.wiki.kernel.org/coccicheck This page shall always refer to the linux-next iteration of scripts/coccicheck. Signed-off-by: Luis R. Rodriguez ---

[PATCH v2 0/5] coccicheck: extend with parmap and indexing heuristics

This v2 addresses the feedback from the v1 series. It also adds 2 more patches, one to document how to add extra additional options and refers to a wiki for further documentation. Luis R. Rodriguez (5): coccicheck: enable parmap support scripts: add glimpse.sh for indexing the kernel

[PATCH v2 4/5] coccicheck: document how to pass extra options to coccinelle

As an example show how to debug your coccinelle script. While at it, fix the case when --profile is passed, when --profile is used we need to ensure --very-quiet is not used. For instance one can use: $ export COCCI=scripts/coccinelle/misc/irqf_oneshot.cocci $ make coccicheck MODE=report

[PATCH v2 2/5] scripts: add glimpse.sh for indexing the kernel

Glimpse is a tool you can use to index the kernel. The tool was recently open sourced under the ISC license and can be obtained at: https://github.com/mcgrof/glimpse.git Signed-off-by: Luis R. Rodriguez --- scripts/glimpse.sh | 12 1 file changed, 12

BPF runtime for systemtap

I'm pleased to be able to announce an initial implementation of an (e)bpf backend for systemtap. For the subset of systemtap probes that can use kprobes, we can use a bpf filter instead of loading a kernel module. As this implementation is young, there are a number of limitations. Neither

[PATCH v2 2/5] scripts: add glimpse.sh for indexing the kernel

Glimpse is a tool you can use to index the kernel. The tool was recently open sourced under the ISC license and can be obtained at: https://github.com/mcgrof/glimpse.git Signed-off-by: Luis R. Rodriguez --- scripts/glimpse.sh | 12 1 file changed, 12 insertions(+) create mode

BPF runtime for systemtap

I'm pleased to be able to announce an initial implementation of an (e)bpf backend for systemtap. For the subset of systemtap probes that can use kprobes, we can use a bpf filter instead of loading a kernel module. As this implementation is young, there are a number of limitations. Neither

[PATCH v2 1/5] coccicheck: enable parmap support

Coccinelle has had parmap support since 1.0.2, this means it supports --jobs, enabling built-in multithreaded functionality, instead of needing one to script it out. Just look for --jobs in the help output to determine if this is supported. Also enable the load balancing to be dynamic, so that if

[PATCH v2 3/5] coccicheck: add indexing enhancement options

Coccinelle has support to make use of its own enhanced "grep" mechanisms instead of using regular grep for searching code, it calls this 'coccigrep'. In lack of any indexing optimization information it uses --use-coccigrep by default. This patch enable indexing optimizations heuristics so that

[PATCH v2 1/5] coccicheck: enable parmap support

Coccinelle has had parmap support since 1.0.2, this means it supports --jobs, enabling built-in multithreaded functionality, instead of needing one to script it out. Just look for --jobs in the help output to determine if this is supported. Also enable the load balancing to be dynamic, so that if

[PATCH v2 3/5] coccicheck: add indexing enhancement options

Coccinelle has support to make use of its own enhanced "grep" mechanisms instead of using regular grep for searching code, it calls this 'coccigrep'. In lack of any indexing optimization information it uses --use-coccigrep by default. This patch enable indexing optimizations heuristics so that

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