On Tue, Aug 9, 2016 at 11:02 AM, Chris Zhong wrote:
> Fix incorrect rk3399 aclk_vio gating bit, it should be 0, not 10. With
> this modification, the aclk_vio_noc should be put into critical list,
> since it is required by VOP.
> And the Type-C DP need these clocks: aclk_hdcp_noc, hclk_hdcp_noc,
From: Joonsoo Kim
This patchset tries to reduce memory waste by page extension user.
First case is architecture supported debug_pagealloc. It doesn't
requires additional memory if guard page isn't used. 8 bytes per
page will be saved in this case.
Second case is related to page owner feature.
The call of iaddr2blockno may fail, so check its return value and
propagate error, if any.
Signed-off-by: Salah Triki
---
fs/befs/datastream.c | 30 --
fs/befs/inode.c | 10 --
fs/befs/io.c | 3 +++
fs/befs/linuxvfs.c |
Check that the allocation group number is not greater or equal to the
number of allocations group in the file system and return BEF_ERR in the
case of error.
Signed-off-by: Salah Triki
---
fs/befs/befs.h | 5 +
1 file changed, 5 insertions(+)
diff --git
Validating the allocation group number is unnecessary since it will
be done by iaddr2blockno().
Signed-off-by: Salah Triki
---
fs/befs/io.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/fs/befs/io.c b/fs/befs/io.c
index 14eef7d..f9790f5 100644
---
The call of iaddr2blockno may fail, so check its return value and
propagate error, if any.
Signed-off-by: Salah Triki
---
fs/befs/datastream.c | 30 --
fs/befs/inode.c | 10 --
fs/befs/io.c | 3 +++
fs/befs/linuxvfs.c | 12 +++-
4
Check that the allocation group number is not greater or equal to the
number of allocations group in the file system and return BEF_ERR in the
case of error.
Signed-off-by: Salah Triki
---
fs/befs/befs.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/fs/befs/befs.h b/fs/befs/befs.h
Validating the allocation group number is unnecessary since it will
be done by iaddr2blockno().
Signed-off-by: Salah Triki
---
fs/befs/io.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/fs/befs/io.c b/fs/befs/io.c
index 14eef7d..f9790f5 100644
--- a/fs/befs/io.c
+++ b/fs/befs/io.c
There is no need to init block, since it will be overwitten later by
iaddr2blockno().
Signed-off-by: Salah Triki
---
fs/befs/io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/befs/io.c b/fs/befs/io.c
index f9790f5..39d0dce 100644
---
There is no need to init block, since it will be overwitten later by
iaddr2blockno().
Signed-off-by: Salah Triki
---
fs/befs/io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/befs/io.c b/fs/befs/io.c
index f9790f5..39d0dce 100644
--- a/fs/befs/io.c
+++ b/fs/befs/io.c
On Wed, Aug 10, 2016 at 4:12 PM, Jon Hunter wrote:
> Where can I see the DT source for this board? There is a
> arch/arm/boot/dts/qcom-apq8060-dragonboard.dts but this does not appear
> to be the same (does not have smsc911x).
There:
On Wed, Aug 10, 2016 at 4:12 PM, Jon Hunter wrote:
> Where can I see the DT source for this board? There is a
> arch/arm/boot/dts/qcom-apq8060-dragonboard.dts but this does not appear
> to be the same (does not have smsc911x).
There:
On Tue, Aug 9, 2016 at 4:32 PM, Chris Zhong wrote:
> This patch adds a binding that describes the Rockchip USB Type-C PHY
> for rk3399
>
> Signed-off-by: Chris Zhong
> Reviewed-by: Tomasz Figa
> Reviewed-by: Kever Yang
On Tue, Aug 9, 2016 at 4:32 PM, Chris Zhong wrote:
> This patch adds a binding that describes the Rockchip USB Type-C PHY
> for rk3399
>
> Signed-off-by: Chris Zhong
> Reviewed-by: Tomasz Figa
> Reviewed-by: Kever Yang
> Acked-by: Rob Herring
Reviewed-by: Guenter Roeck
>
> ---
>
> Changes
On Sat, Aug 06, 2016 at 11:04:51AM +0200, Mike Galbraith wrote:
> On Fri, 2016-08-05 at 13:07 -0400, Tejun Heo wrote:
> > It is true that the trees are semantically different from each other
> > and the symmetric handling of tasks and cgroups is aesthetically
> > pleasing. However, it isn't
On Sat, Aug 06, 2016 at 11:04:51AM +0200, Mike Galbraith wrote:
> On Fri, 2016-08-05 at 13:07 -0400, Tejun Heo wrote:
> > It is true that the trees are semantically different from each other
> > and the symmetric handling of tasks and cgroups is aesthetically
> > pleasing. However, it isn't
On Wed, Aug 10, 2016 at 09:55:39PM +0200, Roman Pen wrote:
> percpu issues some RCU callbacks to synchronize its state, so before
> freeing we have to wait all those callbacks to finish.
>
> E.g. the following simple sequence on stack causes nasty crash:
>
> struct percpu_ref ref;
>
>
On August 9, 2016 11:37:31 PM HST, Richard Ipsum
wrote:
>On Thu, Aug 04, 2016 at 12:40:58PM -1000, Josh Triplett wrote:
>> On Wed, Aug 03, 2016 at 08:12:02PM +0100, Richard Ipsum wrote:
>> > On Thu, Jul 28, 2016 at 11:40:55PM -0700, Josh Triplett wrote:
>> > > I'd
On August 9, 2016 11:37:31 PM HST, Richard Ipsum
wrote:
>On Thu, Aug 04, 2016 at 12:40:58PM -1000, Josh Triplett wrote:
>> On Wed, Aug 03, 2016 at 08:12:02PM +0100, Richard Ipsum wrote:
>> > On Thu, Jul 28, 2016 at 11:40:55PM -0700, Josh Triplett wrote:
>> > > I'd welcome any feedback, whether
On Wed, Aug 10, 2016 at 09:55:39PM +0200, Roman Pen wrote:
> percpu issues some RCU callbacks to synchronize its state, so before
> freeing we have to wait all those callbacks to finish.
>
> E.g. the following simple sequence on stack causes nasty crash:
>
> struct percpu_ref ref;
>
>
On Wed, 2016-08-10 at 11:44 -0700, Jason Low wrote:
> Imre reported an issue where threads are getting starved when trying
> to acquire a mutex. Threads acquiring a mutex can get arbitrarily delayed
> sleeping on a mutex because other threads can continually steal the lock
> in the fastpath and/or
On Wed, 2016-08-10 at 11:44 -0700, Jason Low wrote:
> Imre reported an issue where threads are getting starved when trying
> to acquire a mutex. Threads acquiring a mutex can get arbitrarily delayed
> sleeping on a mutex because other threads can continually steal the lock
> in the fastpath and/or
Coverity reports:
divide_by_zero: In expression readl(dw_wdt->regs + 8) /
clk_get_rate(dw_wdt->clk), division by expression clk_get_rate(dw_wdt->clk)
which may be zero has undefined behavior.
The clock used for the watchdog timer won't change its rate, so read it
only once during probe. Also
Coverity reports:
divide_by_zero: In expression readl(dw_wdt->regs + 8) /
clk_get_rate(dw_wdt->clk), division by expression clk_get_rate(dw_wdt->clk)
which may be zero has undefined behavior.
The clock used for the watchdog timer won't change its rate, so read it
only once during probe. Also
On Wed, 10 Aug 2016, Rafael J. Wysocki wrote:
> So I used your .config to generate one for my test machine and with
> that I can reproduce.
Was that the config I've sent, or did Boris provide one as well? Which one
are you able to reproduce with please?
> The hardware configuration doesn't
On Wed, Aug 10, 2016 at 11:52 PM, Jiri Kosina wrote:
> On Wed, 10 Aug 2016, Thomas Garnier wrote:
>
>> Ok, I want to know if the problem is the PUD alignment or the change
>> of PAGE_OFFSET based all together. Can you test the following change?
>> (on top of everything else with
From: Geert Uytterhoeven
lib/test_hash.c: In function 'test_hash_init':
lib/test_hash.c:146:2: warning: missing braces around initializer
[-Wmissing-braces]
Fixes: 468a9428521e7d00 (": Add support for architecture-specific
functions")
Signed-off-by: Geert Uytterhoeven
On Wed, 10 Aug 2016, Rafael J. Wysocki wrote:
> So I used your .config to generate one for my test machine and with
> that I can reproduce.
Was that the config I've sent, or did Boris provide one as well? Which one
are you able to reproduce with please?
> The hardware configuration doesn't
On Wed, Aug 10, 2016 at 11:52 PM, Jiri Kosina wrote:
> On Wed, 10 Aug 2016, Thomas Garnier wrote:
>
>> Ok, I want to know if the problem is the PUD alignment or the change
>> of PAGE_OFFSET based all together. Can you test the following change?
>> (on top of everything else with KASLR enabled).
From: Geert Uytterhoeven
lib/test_hash.c: In function 'test_hash_init':
lib/test_hash.c:146:2: warning: missing braces around initializer
[-Wmissing-braces]
Fixes: 468a9428521e7d00 (": Add support for architecture-specific
functions")
Signed-off-by: Geert Uytterhoeven
Acked-by: George
Hi,
When upgrading from v4.6 --> v4.7, I lost the display/framebuffer on
OpenRD-Client (the only pcie device on the board).
Bisection points to:
eb13cf8345e94a02e9872ca3e909596a5ddb5f90 is the first bad commit
commit eb13cf8345e94a02e9872ca3e909596a5ddb5f90
Author: Andrew Lunn
A bugfix for the fintek driver required defining some macros, but
one of them clashes with a system header on ARM:
drivers/tty/serial/8250/8250_fintek.c:34:0: error: "IRQ_MODE" redefined
[-Werror]
#define IRQ_MODE 0x70
In file included from /git/arm-soc/arch/arm/include/asm/ptrace.h:13:0,
From: George Spelvin
Geert Uytterhoeven wrote:
> Some versions of gcc don't like tests for the value of an undefined
> preprocessor symbol, even in the #else branch of an #ifndef:
Damn, I had hoped that would work universally; I tried to avoid
Hi,
When upgrading from v4.6 --> v4.7, I lost the display/framebuffer on
OpenRD-Client (the only pcie device on the board).
Bisection points to:
eb13cf8345e94a02e9872ca3e909596a5ddb5f90 is the first bad commit
commit eb13cf8345e94a02e9872ca3e909596a5ddb5f90
Author: Andrew Lunn
Date: Sun Apr
A bugfix for the fintek driver required defining some macros, but
one of them clashes with a system header on ARM:
drivers/tty/serial/8250/8250_fintek.c:34:0: error: "IRQ_MODE" redefined
[-Werror]
#define IRQ_MODE 0x70
In file included from /git/arm-soc/arch/arm/include/asm/ptrace.h:13:0,
From: George Spelvin
Geert Uytterhoeven wrote:
> Some versions of gcc don't like tests for the value of an undefined
> preprocessor symbol, even in the #else branch of an #ifndef:
Damn, I had hoped that would work universally; I tried to avoid the
uglier #if-inside-#ifdef construction. GCC 6
On 8/10/16 12:52 PM, Mark Brown wrote:
On Wed, Aug 10, 2016 at 12:31:28PM -0500, Pierre-Louis Bossart wrote:
If we want to be consistent then we need to have a framework that handles
both the SOC clock sources and the codec internal clock tree (including
dividers and switches)
I wonder if what
On 8/10/16 12:52 PM, Mark Brown wrote:
On Wed, Aug 10, 2016 at 12:31:28PM -0500, Pierre-Louis Bossart wrote:
If we want to be consistent then we need to have a framework that handles
both the SOC clock sources and the codec internal clock tree (including
dividers and switches)
I wonder if what
On Tue, Aug 09, 2016 at 12:53:00PM +0100, Andre Przywara wrote:
> Signed-off-by: Andre Przywara
> ---
> .../devicetree/bindings/mailbox/arm-smc.txt| 53
> ++
> 1 file changed, 53 insertions(+)
> create mode 100644
On Tue, Aug 09, 2016 at 12:53:00PM +0100, Andre Przywara wrote:
> Signed-off-by: Andre Przywara
> ---
> .../devicetree/bindings/mailbox/arm-smc.txt| 53
> ++
> 1 file changed, 53 insertions(+)
> create mode 100644
ARM SMCCC is only set for ARMv7 and ARMv8 CPUs, but we currently
allow the driver to be build for older architecture levels as
well, which results in a link failure:
drivers/gpu/built-in.o: In function `mtk_hdmi_hw_make_reg_writable':
:(.text+0x1e737c): undefined reference to `arm_smccc_smc'
On kernel builds without COMMON_CLK, the newly added mediatek drm
driver fails to build:
drivers/gpu/drm/mediatek/mtk_mipi_tx.c:130:16: error: field 'pll_hw' has
incomplete type
struct clk_hw pll_hw;
^~
In file included from ../include/linux/clk.h:16:0,
Using "make tinyconfig" produces a couple of annoying warnings that show up
for build test machines all the time:
.config:966:warning: override: NOHIGHMEM changes choice state
.config:965:warning: override: SLOB changes choice state
.config:963:warning: override: KERNEL_XZ changes
I could not figure out why, but gcc cannot prove that the
kona_timer_init function always initializes its two outputs,
and we get a warning for the use of the 'lsw' variable later,
which is obviously correct.
drivers/clocksource/bcm_kona_timer.c: In function 'kona_timer_init':
Using "make tinyconfig" produces a couple of annoying warnings that show up
for build test machines all the time:
.config:966:warning: override: NOHIGHMEM changes choice state
.config:965:warning: override: SLOB changes choice state
.config:963:warning: override: KERNEL_XZ changes
I could not figure out why, but gcc cannot prove that the
kona_timer_init function always initializes its two outputs,
and we get a warning for the use of the 'lsw' variable later,
which is obviously correct.
drivers/clocksource/bcm_kona_timer.c: In function 'kona_timer_init':
ARM SMCCC is only set for ARMv7 and ARMv8 CPUs, but we currently
allow the driver to be build for older architecture levels as
well, which results in a link failure:
drivers/gpu/built-in.o: In function `mtk_hdmi_hw_make_reg_writable':
:(.text+0x1e737c): undefined reference to `arm_smccc_smc'
On kernel builds without COMMON_CLK, the newly added mediatek drm
driver fails to build:
drivers/gpu/drm/mediatek/mtk_mipi_tx.c:130:16: error: field 'pll_hw' has
incomplete type
struct clk_hw pll_hw;
^~
In file included from ../include/linux/clk.h:16:0,
When CONFIG_NET_DSA_HWMON is disabled, we get warnings about two unused
functions whose only callers are all inside of an #ifdef:
drivers/net/dsa/mv88e6xxx.c:3257:12: 'mv88e6xxx_mdio_page_write' defined but
not used [-Werror=unused-function]
drivers/net/dsa/mv88e6xxx.c:3244:12:
The mediatek DRM driver can be configured for compile testing with
CONFIG_OF disabled, but then fails to link:
drivers/gpu/built-in.o: In function `mtk_drm_bind':
analogix_dp_reg.c:(.text+0x52888): undefined reference to
`of_find_device_by_node'
analogix_dp_reg.c:(.text+0x52930): undefined
When CONFIG_NET_DSA_HWMON is disabled, we get warnings about two unused
functions whose only callers are all inside of an #ifdef:
drivers/net/dsa/mv88e6xxx.c:3257:12: 'mv88e6xxx_mdio_page_write' defined but
not used [-Werror=unused-function]
drivers/net/dsa/mv88e6xxx.c:3244:12:
The mediatek DRM driver can be configured for compile testing with
CONFIG_OF disabled, but then fails to link:
drivers/gpu/built-in.o: In function `mtk_drm_bind':
analogix_dp_reg.c:(.text+0x52888): undefined reference to
`of_find_device_by_node'
analogix_dp_reg.c:(.text+0x52930): undefined
On Mon, Aug 08, 2016 at 02:08:49PM +0800, Wenyou Yang wrote:
> Due the driver improvements, update the properties,
> - Remove "active-semi,check-battery-temperature" property.
> - Add the properties, "active-semi,irq_gpio"
>and "active-semi,lbo-gpios".
>
> Signed-off-by: Wenyou Yang
On Mon, Aug 08, 2016 at 02:08:49PM +0800, Wenyou Yang wrote:
> Due the driver improvements, update the properties,
> - Remove "active-semi,check-battery-temperature" property.
> - Add the properties, "active-semi,irq_gpio"
>and "active-semi,lbo-gpios".
>
> Signed-off-by: Wenyou Yang
> ---
This is a set of patches to address build warnings and errors that have
come up in linux-4.8 but that worked fine in v4.7. I've added the
tinyconfig warning patch in there as well, which is not a regression
but is something that shows up in the kernelci.org build bots.
The other patches address
This is a set of patches to address build warnings and errors that have
come up in linux-4.8 but that worked fine in v4.7. I've added the
tinyconfig warning patch in there as well, which is not a regression
but is something that shows up in the kernelci.org build bots.
The other patches address
On Wed, 10 Aug 2016, Thomas Garnier wrote:
> Ok, I want to know if the problem is the PUD alignment or the change
> of PAGE_OFFSET based all together. Can you test the following change?
> (on top of everything else with KASLR enabled). It will randomize the
> memory sections only on PGD level.
>
On Wed, 10 Aug 2016, Thomas Garnier wrote:
> Ok, I want to know if the problem is the PUD alignment or the change
> of PAGE_OFFSET based all together. Can you test the following change?
> (on top of everything else with KASLR enabled). It will randomize the
> memory sections only on PGD level.
>
*MIGHT_HAVE_PCI* config is already selected in ARCH_MULTIPLATFORM.
Fix it from getting redundantly selected in all
ARCH_MULTIPLATFORM based machines.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Alexandre Belloni
---
*MIGHT_HAVE_PCI* config is already selected in ARCH_MULTIPLATFORM.
Fix it from getting redundantly selected in all
ARCH_MULTIPLATFORM based machines.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Alexandre Belloni
---
arch/arm/mach-at91/Kconfig |1 -
arch/arm/mach-axxia/Kconfig
On Tue, Aug 09, 2016 at 11:01:23PM +0100, Luis de Bethencourt wrote:
> befs_dump_super_block() wasn't giving the inode_size information when
> dumping all elements of the superblock. Add this element to have complete
> information of the superblock.
>
> Signed-off-by: Luis de Bethencourt
If net namespace is attached to a user namespace let's make container's
root owner of sysctls affecting said network namespace instead of global
root.
This also allows us to clean up net_ctl_permissions() because we do not
need to fudge permissions anymore for the container's owner since it now
On Tue, Aug 09, 2016 at 11:01:25PM +0100, Luis de Bethencourt wrote:
> The description of befs_load_sb was confusing the kernel-doc system since,
> because it starts with /**, it thinks it will document the function with
> kernel-doc formatting. Which it isn't.
>
> Fix other comment style issues
On Tue, Aug 09, 2016 at 11:13:27AM +0200, Neil Armstrong wrote:
> Add documentations and dt-bindings headers for the AO clock and reset
> controller.
>
> Signed-off-by: Neil Armstrong
> ---
> .../bindings/clock/amlogic,gxbb-aoclkc.txt | 45 +++
>
On Wed, Aug 10, 2016 at 12:50 PM, Kyle Huey wrote:
> This fixes rr. It doesn't quite fix the provided testcase, because the
> testcase fails to wait on the tracee after awakening from the nanosleep.
> Instead the testcase immediately does a PTHREAD_CONT, discarding the
>
Guided by grsecurity's analogous __read_only markings in arch/arm,
this applies several uses of __ro_after_init to structures that are
only updated during __init.
Signed-off-by: Kees Cook
---
v2:
- drop vector table for now due to FIQ updates, rmk
---
Hi, Peter
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Peter Chen
> Sent: Wednesday, August 10, 2016 11:12 AM
> To: Stephen Boyd
> Cc: Peter Chen ;
When CONFIG_NET_NS is disabled, registering pernet operations causes
init() to be called immediately with init_net as an argument. Unfortunately
this leads to some pernet ops, such as proc_net_ns_init() to be called too
early, when init_net namespace has not been fully initialized. This causes
On Wed, Aug 10, 2016 at 12:41 PM, Arnd Bergmann wrote:
> On Wednesday, August 10, 2016 11:32:07 AM CEST Kees Cook wrote:
>> On Wed, Aug 10, 2016 at 2:43 AM, Russell King - ARM Linux
>> wrote:
>> > On Fri, Jun 03, 2016 at 11:40:24AM -0700, Kees Cook wrote:
>>
Guided by grsecurity's analogous __read_only markings in arch/arm,
this applies several uses of __ro_after_init to structures that are
only updated during __init.
Signed-off-by: Kees Cook
---
v2:
- drop vector table for now due to FIQ updates, rmk
---
arch/arm/kernel/cpuidle.c | 2 +-
Hi, Peter
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of Peter Chen
> Sent: Wednesday, August 10, 2016 11:12 AM
> To: Stephen Boyd
> Cc: Peter Chen ; gre...@linuxfoundation.org;
> st...@rowland.harvard.edu;
When CONFIG_NET_NS is disabled, registering pernet operations causes
init() to be called immediately with init_net as an argument. Unfortunately
this leads to some pernet ops, such as proc_net_ns_init() to be called too
early, when init_net namespace has not been fully initialized. This causes
On Wed, Aug 10, 2016 at 12:41 PM, Arnd Bergmann wrote:
> On Wednesday, August 10, 2016 11:32:07 AM CEST Kees Cook wrote:
>> On Wed, Aug 10, 2016 at 2:43 AM, Russell King - ARM Linux
>> wrote:
>> > On Fri, Jun 03, 2016 at 11:40:24AM -0700, Kees Cook wrote:
>> >> @@ -1309,16 +1309,11 @@ void
On Tue, Aug 09, 2016 at 11:01:25PM +0100, Luis de Bethencourt wrote:
> The description of befs_load_sb was confusing the kernel-doc system since,
> because it starts with /**, it thinks it will document the function with
> kernel-doc formatting. Which it isn't.
>
> Fix other comment style issues
On Tue, Aug 09, 2016 at 11:13:27AM +0200, Neil Armstrong wrote:
> Add documentations and dt-bindings headers for the AO clock and reset
> controller.
>
> Signed-off-by: Neil Armstrong
> ---
> .../bindings/clock/amlogic,gxbb-aoclkc.txt | 45 +++
>
On Wed, Aug 10, 2016 at 12:50 PM, Kyle Huey wrote:
> This fixes rr. It doesn't quite fix the provided testcase, because the
> testcase fails to wait on the tracee after awakening from the nanosleep.
> Instead the testcase immediately does a PTHREAD_CONT, discarding the
> PTHREAD_EVENT_EXIT.
On Tue, Aug 09, 2016 at 11:01:23PM +0100, Luis de Bethencourt wrote:
> befs_dump_super_block() wasn't giving the inode_size information when
> dumping all elements of the superblock. Add this element to have complete
> information of the superblock.
>
> Signed-off-by: Luis de Bethencourt
> ---
>
If net namespace is attached to a user namespace let's make container's
root owner of sysctls affecting said network namespace instead of global
root.
This also allows us to clean up net_ctl_permissions() because we do not
need to fudge permissions anymore for the container's owner since it now
Currently [almost] all /proc objects belong to the global root, even if
data belongs to a given namespace within a container and (at least for
sysctls) we work around permssions checks to allow container's root to
access the data.
This series changes ownership of net namespace /proc objects
There are certain parameters that belong to net namespace and that are
exported in /proc. They should be controllable by the container's owner,
but are currently owned by global root and thus not available.
Let's change proc code to inherit ownership of parent entry, and when
create per-ns "net"
On Wednesday, August 10, 2016 10:43:39 AM CEST Russell King - ARM Linux wrote:
> On Fri, Jun 03, 2016 at 11:40:24AM -0700, Kees Cook wrote:
> > @@ -1309,16 +1309,11 @@ void __init arm_mm_memblock_reserve(void)
> > * Any other function or debugging method which may touch any device _will_
> > *
There are certain parameters that belong to net namespace and that are
exported in /proc. They should be controllable by the container's owner,
but are currently owned by global root and thus not available.
Let's change proc code to inherit ownership of parent entry, and when
create per-ns "net"
On Wednesday, August 10, 2016 10:43:39 AM CEST Russell King - ARM Linux wrote:
> On Fri, Jun 03, 2016 at 11:40:24AM -0700, Kees Cook wrote:
> > @@ -1309,16 +1309,11 @@ void __init arm_mm_memblock_reserve(void)
> > * Any other function or debugging method which may touch any device _will_
> > *
Currently [almost] all /proc objects belong to the global root, even if
data belongs to a given namespace within a container and (at least for
sysctls) we work around permssions checks to allow container's root to
access the data.
This series changes ownership of net namespace /proc objects
On Tue, Aug 09, 2016 at 11:01:26PM +0100, Luis de Bethencourt wrote:
> Fixing the following checkpatch.pl error:
>
> ERROR: "foo * bar" should be "foo *bar"
> +befs_load_sb(struct super_block *sb, befs_super_block * disk_sb)
>
> And the following warnings:
>
> WARNING: suspect code indent for
On Tue, Aug 09, 2016 at 11:01:26PM +0100, Luis de Bethencourt wrote:
> Fixing the following checkpatch.pl error:
>
> ERROR: "foo * bar" should be "foo *bar"
> +befs_load_sb(struct super_block *sb, befs_super_block * disk_sb)
>
> And the following warnings:
>
> WARNING: suspect code indent for
Since we have to write ddb allocations at the same time as we do other
plane updates, we're going to need to be able to control the order in
which we execute modesets on each pipe. The easiest way to do this is to
just factor this section of intel_atomic_commit_tail()
(intel_atomic_commit() for
Fix to return error code -ENOMEM instead of 0 when create card
failed, as done elsewhere in this function.
Fixes: 45fb6b6f2aa3 ("ASoC: sunxi: add support for the on-chip
codec on early Allwinner SoCs")
Signed-off-by: Wei Yongjun
---
sound/soc/sunxi/sun4i-codec.c | 1 +
1
Hi,
It seems like a false alarm. The 0-DAY tree does not contain the same content
as regmap/for-next tree.
>From the patch series "regmap: debugfs: Add support for dumping write only
>device registers the" the PATCH v2 1/2 is missing form 0-DAY tree while the
>PATCH v2 2/2 is applied. This
Hi,
On 19/07/16 13:40, Juri Lelli wrote:
> Hi all,
>
> version 6 of "CPUs capacity information for heterogeneous systems" patchset
> [1]
> (please refer to previous postings to get some context).
>
gentle ping to everybody participating in this discussion.
Rob acked the bindings and Peter
Fixes crash at boot for me.
Small nit wrt subj
s/def/deref/
Commit-ID: bd425d4bfc7a1a6064dbbadfbac9c7eec0e426ec
Gitweb: http://git.kernel.org/tip/bd425d4bfc7a1a6064dbbadfbac9c7eec0e426ec
Author: Morten Rasmussen
AuthorDate: Wed, 22 Jun 2016 18:03:12 +0100
Committer: Ingo Molnar
CommitDate: Wed, 10 Aug
This file describes pxa25x SoCs. Not all devices are listed yet, only
the subset which was already tested with a lubbock board.
Signed-off-by: Robert Jarzmik
---
arch/arm/boot/dts/pxa25x.dtsi | 92 +++
1 file changed, 92
Commit-ID: a1fd46565bea62840a24bee7b7c60f65bb12bd21
Gitweb: http://git.kernel.org/tip/a1fd46565bea62840a24bee7b7c60f65bb12bd21
Author: Leo Yan
AuthorDate: Fri, 5 Aug 2016 14:32:38 +0800
Committer: Ingo Molnar
CommitDate: Wed, 10 Aug 2016 14:03:32
Since kswapd compaction moved to kcompactd, compact_pgdat() is not called
anymore, so we remove it. The only caller of __compact_pgdat() is
compact_node(), so we merge them and remove code that was only reachable from
kswapd.
Signed-off-by: Vlastimil Babka
Acked-by: Michal Hocko
Now that we can hook into update_crtcs and control the order in which we
update CRTCs at each modeset, we can finish the final step of fixing
Skylake's watermark handling by performing DDB updates at the same time
as plane updates and watermark updates.
The first major change in this patch is
The __compaction_suitable() function checks the low watermark plus a
compact_gap() gap to decide if there's enough free memory to perform
compaction. Then __isolate_free_page uses low watermark check to decide if
particular free page can be isolated. In the latter case, using low watermark
is
Hello,
On Wed, 10 Aug 2016 10:09:08 +0200, Gregory CLEMENT wrote:
> While converting the init function to return an error, the wrong clock
> was get. This lead to wrong clock rate and slow down the kernel. For
> example, before the patch a typical boot was around 15s after it was 1
> minute
On 8/10/2016 15:12, Hans Verkuil wrote:
On 08/10/2016 07:36 AM, Wu, Songjun wrote:
On 8/8/2016 17:56, Hans Verkuil wrote:
On 08/08/2016 11:37 AM, Hans Verkuil wrote:
On 08/03/2016 10:08 AM, Songjun Wu wrote:
Add driver for the Image Sensor Controller. It manages
incoming data from a
Since we have to write ddb allocations at the same time as we do other
plane updates, we're going to need to be able to control the order in
which we execute modesets on each pipe. The easiest way to do this is to
just factor this section of intel_atomic_commit_tail()
(intel_atomic_commit() for
301 - 400 of 1870 matches
Mail list logo