4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Lokesh Vutla
commit 3ca4a238106dedc285193ee47f494a6584b6fd2f upstream.
Commit 127500ccb766f ("ARM: OMAP2+: Only write the sysconfig on id
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vladis Dronov
commit 162f98dea487206d9ab79fc12ed64700667a894d upstream.
The gtco driver expects at least one valid endpoint. If given mal
On Sun, Apr 17, 2016 at 01:36:55PM -0400, Sinan Kaya wrote:
> acpi_irq_get_penalty is now calculating the penalty on the fly now.
> No need to maintain global list of penalties or calculate them
> at the init time. Removing duplicate code in acpi_irq_penalty_init.
>
> Signed-off-by: Sinan Kaya
>
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Andy Shevchenko
commit 4f4bc0abff79dc9d7ccbd3143adbf8ad1f4fe6ab upstream.
There is a typo in documentation regarding to descriptor empty
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Sebastian Ott
commit 9d89d9e61d361f3adb75e1aebe4bb367faf16cfa upstream.
Newer machines might use a different (larger) format for function
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Emmanuel Grumbach
commit 9fc515bc9e735c10cd327f05c20f5ef69474188d upstream.
IWL_INFO is not an error but still printed by default.
"can't
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Patrick Uiterwijk
commit 199831c77c50e6913e893b6bc268ba9f4a9a2bf8 upstream.
The USB2 port for Armada 38x is defined to be at 58000, not a
On Tue, 26 Apr 2016 18:55:38 +0100, Al Viro said:
> It is a change of user-visible behaviour, but I would be very
> surprised if anything broke from that change. And it would help to simplify
> the awful mess we have in there.
I have to admit that over the past 3 decades of working with Un
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Sergei Shtylyov
[ Upstream commit c1b7fca65070bfadca94dd53a4e6b71cd4f69715 ]
In a low memory situation, if netdev_alloc_skb() fails on a
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Haishuang Yan
[ Upstream commit 5745b8232e942abd5e16e85fa9b27cc21324acf0 ]
pskb_may_pull() can change skb->data, so we have to load ptr/o
On 04/15/2016 11:07 AM, Mel Gorman wrote:
Every page allocated or freed is checked for sanity to avoid corruptions
that are difficult to detect later. A bad page could be due to a number of
fields. Instead of using multiple branches, this patch combines multiple
fields into a single branch. A de
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Alan Stern
commit 972e6a993f278b416a8ee3ec65475724fc36feb2 upstream.
The usbhid driver has inconsistently duplicated code in its post-res
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Haishuang Yan
[ Upstream commit be447f305494e019dfc37ea4cdf3b0e4200b4eba ]
pskb_may_pull() can change skb->data, so we have to load ptr/o
On 04/15/2016 11:07 AM, Mel Gorman wrote:
The original count is never reused so it can be removed.
Signed-off-by: Mel Gorman
Acked-by: Vlastimil Babka
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Daniel Borkmann
[ Upstream commit 5a5abb1fa3b05dd6aa821525832644c1e7d2905f ]
Sasha Levin reported a suspicious rcu_dereference_protected(
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: "subas...@codeaurora.org"
[ Upstream commit 071d36bf21bcc837be00cea55bcef8d129e7f609 ]
A crash is observed when a decrypted packet is pro
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: =?UTF-8?q?Bj=C3=B8rn=20Mork?=
[ Upstream commit e84810c7b85a2d7897797b3ad3e879168a8e032a ]
Thomas reports:
"Windows:
00 diagnostics
01 m
On Sat, Apr 16, 2016 at 12:03:39PM +0100, Gabriele Paoloni wrote:
> Currently dw_pcie_setup_rc configures memory base and memory
> limit in the type1 configuration header for the root complex.
> In doing so it uses the cpu address (pp->mem_base) rather than
> the bus address (pp->mem_bus_addr): thi
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Arnd Bergmann
[ Upstream commit e725a66c0202b5f36c2f9d59d26a65c53bbf21f7 ]
gcc-6 finds an out of bounds access in the fst_add_one functio
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Manish Chopra
[ Upstream commit 2c9a266afefe137bff06bbe0fc48b4d3b3cb348c ]
When running small packets [length < 256 bytes] traffic, packe
Hi1
> > When dropping the add_disk_randomness function in the legacy /dev/random, I
> > would assume that without changes to add_input_randomness and
> > add_interrupt_randomness, we become even more entropy-starved.
>
> Sure, but your system isn't doing anything magical here. The main
> diffe
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Willem de Bruijn
[ Upstream commit 2793a23aacbd754dbbb5cb75093deb7e4103bace ]
Netdevice parameter hard_header_len is variously interprete
On Mon 2016-04-25 13:06:29, Steven Rostedt wrote:
> Over the weekend my server was acting funny. The display wasn't working
> well, and I assumed that a driver was going bad. I went to look at the
> kernel dmesg, but the buffer only had the following over and over:
>
> [226062.401405] systemd-logi
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Eric Dumazet
[ Upstream commit fe30937b65354c7fec244caebbdaae68e28ca797 ]
bond_get_stats() can be called from rtnetlink (with RTNL held)
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Xin Long
[ Upstream commit 40b4f0fd74e46c017814618d67ec9127ff20f157 ]
As the member .cmp_addr of sctp_af_inet6, sctp_v6_cmp_addr should a
On 2016-04-19 18:53, Al Stone wrote:
On 04/19/2016 02:12 PM, Ashwin Chaugule wrote:
+ Ryan
Hi Al,
On 18 April 2016 at 20:11, Al Stone wrote:
When CPPC is being used by ACPI on arm64, user space tools such as
cpupower report CPU frequency values from sysfs that are incorrect.
What the driver
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: =?UTF-8?q?Bj=C3=B8rn=20Mork?=
[ Upstream commit bf13c94ccb33c3182efc92ce4989506a0f541243 ]
The MC74xx and EM74xx modules use different ID
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Willem de Bruijn
[ Upstream commit ea47781c26510e5d97f80f9aceafe9065bd5e3aa ]
As variable length protocol, AX25 fails link layer header v
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Willem de Bruijn
[ Upstream commit 9ed988cd591500c040b2a6257bc68543e08ceeef ]
Replace link layer header validation check ll_header_trunca
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Bernie Harris
[ Upstream commit 5146d1f151122e868e594c7b45115d64825aee5f ]
IPCB may contain data from previous layers (in the observed ca
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Oliver Neukum
commit 1666984c8625b3db19a9abc298931d35ab7bc64b upstream.
In case bind() works, but a later error forces bailing
in probe()
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Bill Sommerfeld
[ Upstream commit 59dca1d8a6725a121dae6c452de0b2611d5865dc ]
IPv4 interprets a negative return value from a protocol hand
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Stefan Wahren
[ Upstream commit a4690afeb0d2d7ba4d60dfa98a89f3bb1ce60ecd ]
ether_setup sets IFF_TX_SKB_SHARING but this is not supported
4.2.8-ckt9 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Diego Viola
[ Upstream commit ee50c130c82175eaa0820c96b6d3763928af2241 ]
The JMC260 network card fails to suspend/resume because the call
On 2016/04/26 10:02, Steven Rostedt wrote:
> On Sat, 2 Apr 2016 10:55:22 -0700
> Benjamin Poirier wrote:
>
> > When using `make localmodconfig` and friends, if the input config comes
> > from a kernel that was built in a different environment (for example, the
> > canonical case of using localmo
On Tue, Apr 26, 2016 at 6:49 PM, Arnd Bergmann wrote:
> On Tuesday 26 April 2016 17:41:45 Saeed Mahameed wrote:
>> On Tue, Apr 26, 2016 at 4:53 PM, Arnd Bergmann wrote:
>> >
>> > Sure, do you want to just edit this when you forward the patch, or
>> > do you need me to do it?
>> >
>>
>> Well, I wo
When using `make localmodconfig` and friends, if the input config comes
from a kernel that was built in a different environment (for example, the
canonical case of using localmodconfig to trim a distribution kernel
config) the key files for module signature checking will not be available
and should
On Tue, 26 Apr 2016 20:36:16 +0200
Rafał Miłecki wrote:
> Our array nand_ecc_algos doesn't specify mappings for all available
> enum nand_ecc_algo values. The one missing there is NAND_ECC_UNKNOWN
> as this value is reserved for algorithm not being specified at all.
> It means we have to be caref
On Tue, Apr 26, 2016 at 6:52 PM, Arnd Bergmann wrote:
> struct mlx5e_channel_param is a large structure that is allocated
> on the stack of mlx5e_open_channels, and with a recent change
> it has grown beyond the warning size for the maximum stack
> that a single function should use:
>
> mellanox/m
On Tue, Apr 26, 2016 at 08:23:46PM +0200, Daniel Vetter wrote:
> On Tue, Apr 26, 2016 at 08:40:45PM +0300, Ville Syrjälä wrote:
> > On Tue, Apr 26, 2016 at 07:20:49PM +0200, Daniel Vetter wrote:
> > > On Tue, Apr 26, 2016 at 07:26:21PM +0300, Ville Syrjälä wrote:
> > > > On Tue, Apr 26, 2016 at 04:
Am Dienstag, 26. April 2016, 20:44:39 schrieb Pavel Machek:
Hi Pavel,
> Hi1
>
> > > When dropping the add_disk_randomness function in the legacy
> > > /dev/random, I
> > > would assume that without changes to add_input_randomness and
> > > add_interrupt_randomness, we become even more entropy-st
On 2016/04/26 11:11, Steven Rostedt wrote:
> On Sun, 10 Apr 2016 17:06:33 -0700
> Benjamin Poirier wrote:
>
> > Note that this may change the resulting .config, causing it to have fewer
> > symbols turned on. Before this patch we incorrectly identified some symbols
> > as not having a prompt and
Also recognize standalone "prompt".
Before this patch we incorrectly identified some symbols as not having a
prompt and potentially needing to be selected by something else.
Note that this patch could theoretically change the resulting .config,
causing it to have fewer symbols turned on. However,
Hi,
v4.6-rc solidly hangs after a short while after boot, login to X11, and
doing nothing much remarkable on the just brought up X desktop.
Hardware: x86-64, E3-1245 v3 (Haswell),
mainboard Supermicro X10SAE,
using integrated Intel graphics (HD P4600, i915 driver),
C
On Mon 2016-04-25 20:34:07, Jarkko Sakkinen wrote:
> Intel(R) SGX is a set of CPU instructions that can be used by
> applications to set aside private regions of code and data. The code
> outside the enclave is disallowed to access the memory inside the
> enclave by the CPU access control.
>
> Th
On 4/26/2016 2:36 PM, Bjorn Helgaas wrote:
> On Sun, Apr 17, 2016 at 01:36:53PM -0400, Sinan Kaya wrote:
>> Code has been redesigned to calculate penalty requirements on the fly. This
>> significantly simplifies the implementation and removes some of the init
>> calls from x86 architecture.
>>
>> S
On Tue, Apr 26, 2016 at 02:41:37PM -0400, valdis.kletni...@vt.edu wrote:
> On Tue, 26 Apr 2016 18:55:38 +0100, Al Viro said:
>
> > It is a change of user-visible behaviour, but I would be very
> > surprised if anything broke from that change. And it would help to simplify
> > the awful mess w
On Apr 26 Stefan Richter wrote:
> Hardware: x86-64, E3-1245 v3 (Haswell),
> mainboard Supermicro X10SAE,
> using integrated Intel graphics (HD P4600, i915 driver),
> C226 PCH's AHCI and USB 2/3, ASMedia ASM1062 AHCI,
> Intel LAN (i217, igb driver),
>
Add support for tracing the MMIO helpers readl()/writel() (and their
variants), for use while developing and debugging device drivers.
The address and the value are saved along with the C expressions used in
the driver when calling these MMIO access functions, leading to a trace
of the driver's in
On Tue, Apr 26, 2016 at 12:00 PM, Pavel Machek wrote:
> On Mon 2016-04-25 20:34:07, Jarkko Sakkinen wrote:
>> Intel(R) SGX is a set of CPU instructions that can be used by
>> applications to set aside private regions of code and data. The code
>> outside the enclave is disallowed to access the me
g write buffer coherency: ok
> CPU0: thread -1, cpu 0, socket 0, mpidr 8000
>
>
> RCU used illegally from idle CPU!
> rcu_scheduler_active = 1, debug_locks = 0
> RCU used illegally from extended quiescent state!
> no locks held by swapper/1/0.
>
> stack backtrace:
On Tue, Apr 26, 2016 at 03:20:32PM -0300, Arnaldo Carvalho de Melo wrote:
> Yeah, and that already works in perf, its just that it doesn't work from some
> points (PERF_TYPE_SOFTWARE, PERF_TYPE_TRACEPOINT, etc), as described in the
> changeset I mentioned.
Look at it the other way around, it _only
On Apr 26 Stefan Richter wrote:
> v4.6-rc solidly hangs after a short while after boot, login to X11, and
> doing nothing much remarkable on the just brought up X desktop.
>
> Hardware: x86-64, E3-1245 v3 (Haswell),
> mainboard Supermicro X10SAE,
> using integrated Intel graphi
On 04/15/2016 11:07 AM, Mel Gorman wrote:
The function call overhead of get_pfnblock_flags_mask() is measurable in
the page free paths. This patch uses an inlined version that is faster.
Signed-off-by: Mel Gorman
Acked-by: Vlastimil Babka
On Tue, 26 Apr 2016 14:00:11 +0100 Mel Gorman
wrote:
> If Andrew is watching, please drop this patch if possible.
Thud.
On 04/26/2016 03:46 PM, Florian Vallee wrote:
According to the m_can user manual changelog the BTP register layout was
updated with core revision 3.1.0
Hello Florian,
nice to see a real v3.1.0 user emerging on the mailing list :-)
I wonder whether this small change covers the updates made bet
On Tuesday 26 April 2016 21:04:42 Rabin Vincent wrote:
> Add support for tracing the MMIO helpers readl()/writel() (and their
> variants), for use while developing and debugging device drivers.
>
> The address and the value are saved along with the C expressions used in
> the driver when calling t
0, socket 0, mpidr 8000
>
>
> RCU used illegally from idle CPU!
> rcu_scheduler_active = 1, debug_locks = 0
> RCU used illegally from extended quiescent state!
> no locks held by swapper/1/0.
>
> stack backtrace:
> CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.6.0-rc5-next-201
On 04/26/2016 01:13 PM, Tony Lindgren wrote:
> Are any of these needed for the v4.6-rc cycle?
I understand that these are arriving a little late especially if we don't get
to rc7. However, it would be great if these could get in the v4.6 kernel
release. They shouldn't be too risky to anyone, but
The following changes since commit 0b24f7a8d6e0d17bcf24433ce5827841a05b5b46:
Merge tag 'mvebu-fixes-4.6-1' of git://git.infradead.org/linux-mvebu into
fixes (2016-04-12 12:35:07 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tag
On AMD CPUs, a failed loadsegment currently may not clear the FS
base. Fix it.
While we're at it, prevent loadsegment(gs, xyz) from even compiling
on 64-bit kernels. It shouldn't be used.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/segment.h | 42 ++
Now that set_thread_area is supposed to give deterministic behavior
when it modifies in-use segments, test it.
Signed-off-by: Andy Lutomirski
---
tools/testing/selftests/x86/ldt_gdt.c | 250 ++
1 file changed, 250 insertions(+)
diff --git a/tools/testing/selftest
As far as I know, the optimization doesn't work on any modern distro
because modern distros use high addresses for ASLR. Remove it.
The ptrace code was either wrong or very strange, but the behavior
with this patch should be essentially identical to the behavior
without this patch unless user cod
Unlike ds and es, these are base addresses, not selectors. Rename
them so their meaning is more obvious.
On x86_32, the field is still called fs. Fixing that could make sense
as a future cleanup.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/elf.h | 6 +++---
arch/x86/include
The current behavior of set_thread_area when it modifies a segment that is
currently loaded is a bit confused.
If CS [1] or SS is modified, the change will take effect on return
to userspace because CS and SS are fundamentally always reloaded on
return to userspace.
Similarly, on 32-bit kernels,
asm/alternative.h isn't directly useful from assembly, but it
shouldn't break the build.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/alternative.h | 4
1 file changed, 4 insertions(+)
diff --git a/arch/x86/include/asm/alternative.h
b/arch/x86/include/asm/alternative.h
index be
On Tue, 26 Apr 2016 20:02:48 +0100, Al Viro said:
> > The biggest danger I can see is some shell script doing something like:
> >
> > foobar > $dir/$targetfile
> >
> > and $targetfile is unset. If we allow a program to get an open fd that
> > refers
> > to a directory, what are the semantics of v
alternative.h pulls in ptrace.h, which means that alternatives can't
be used in anything referenced from ptrace.h, which is a mess.
Break the dependency by pulling text patching helpers into their own
header.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/alternative.h | 33 -
On AMD CPUs, a failed load_gs_base currently may not clear the FS
base. Fix it.
Signed-off-by: Andy Lutomirski
---
arch/x86/entry/entry_64.S | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S
index 1693c17dbf81..6344629ae1ce 100644
--
On Tuesday 26 April 2016 20:23:35 Andrew Lunn wrote:
> > A more complex problem would be having a PHY driver for a device
> > that can be either an ethernet phy or some other phy.
>
> I doubt that ever happens. You can have up to 32 different devices on
> an MDIO bus. Since an Ethernet PHY and a "
Hi all-
This is preparation for enabling FSGSBASE and fixing FS/GS switching
better than my last attempt.
It cleans up the code, fixes two more holes in X86_BUG_NULL_SEG
handling (loadsegment(fs, val) and load_gs_index(val) failure
handling), and makes set_thread_area behave in a well-defined
man
On 2016-04-26 14:10, Davidlohr Bueso wrote:
On Tue, 26 Apr 2016, Austin S. Hemmelgarn wrote:
At the absolute minimum, we should be logging (at least at a warning
level) that we had to fall back the the backup GPT. If somebody is
dealing with a disk that had a torn write to the primary GPT, tha
On Tue, 26 Apr 2016 21:14:47 +0200
Arnd Bergmann wrote:
> > +/* This part must be outside protection */
> > +#include
> > diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
> > index e45db6b0d878..feca834436c5 100644
> > --- a/kernel/trace/Kconfig
> > +++ b/kernel/trace/Kconfig
> > @@ -37
th this patch applied, 4.6.0-rc5-next-20160426 fails to boot on
rk3288-veyron devices with the bug below. Reverting this one patch
results in the system booting again:
[1.059661] [ cut here ]
[1.064272] kernel BUG at drivers/regulator/helpers.c:255!
[1.069750] Inter
Unprivileged users should not be able to mount block devices when
they lack sufficient privileges towards the block device inode.
Update blkdev_get_by_path() to validate that the user has the
required access to the inode at the specified path. The check
will be skipped for CAP_SYS_ADMIN, so privile
The SMACK64, SMACK64EXEC, and SMACK64MMAP labels are all handled
differently in untrusted mounts. This is confusing and
potentically problematic. Change this to handle them all the same
way that SMACK64 is currently handled; that is, read the label
from disk and check it at use time. For SMACK64 an
From: Pavel Tikhomirov
We probably need to fix superblock leak in patch (v4 "fs: Add user
namesapace member to struct super_block"):
Imagine posible code path in sget_userns: we iterate through
type->fs_supers and do not find suitable sb, we drop sb_lock to
allocate s and go to retry. After we d
Superblock level remounts are currently restricted to global
CAP_SYS_ADMIN, as is the path for changing the root mount to
read only on umount. Loosen both of these permission checks to
also allow CAP_SYS_ADMIN in any namespace which is privileged
towards the userns which originally mounted the file
Signed-off-by: Seth Forshee
Acked-by: Miklos Szeredi
---
fs/fuse/inode.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index 0a771145d853..254f1944ee98 100644
--- a/fs/fuse/inode.c
+++ b/fs/fuse/inode.c
@@ -1199,7 +1199,7 @@ static void
A privileged user in s_user_ns will generally have the ability to
manipulate the backing store and insert security.* xattrs into
the filesystem directly. Therefore the kernel must be prepared to
handle these xattrs from unprivileged mounts, and it makes little
sense for commoncap to prevent writing
When the userspace process servicing fuse requests is running in
a pid namespace then pids passed via the fuse fd are not being
translated into that process' namespace. Translation is necessary
for the pid to be useful to that process.
Since no use case currently exists for changing namespaces all
Unprivileged users are normally restricted from mounting with the
allow_other option by system policy, but this could be bypassed
for a mount done with user namespace root permissions. In such
cases allow_other should not allow users outside the userns
to access the mount as doing so would give the
On 04/26/2016 07:02 PM, Liviu Dudau wrote:
> On Tue, Apr 26, 2016 at 06:28:52PM +0300, Grygorii Strashko wrote:
>
> Hi Grygorii,
>
> First time I'm seeing this patch, so I have a few questions, mostly
> related to the commit message:
Hm. You are in cc for RFC.
Sry, forgot to add link [1].
>
>>
In order to support mounts from namespaces other than
init_user_ns, fuse must translate uids and gids to/from the
userns of the process servicing requests on /dev/fuse. This
patch does that, with a couple of restrictions on the namespace:
- The userns for the fuse connection is fixed to the names
In a userns mount some on-disk inodes may have ids which do not
map into s_user_ns, in which case the in-kernel inodes are owned
by invalid users. The superblock owner should be able to change
attributes of these inodes but cannot. However it is unsafe to
grant the superblock owner privileged acces
ids in on-disk ACLs should be converted to s_user_ns instead of
init_user_ns as is done now. This introduces the possibility for
id mappings to fail, and when this happens syscalls will return
EOVERFLOW.
Signed-off-by: Seth Forshee
Acked-by: Serge Hallyn
---
fs/posix_acl.c | 67
From: Andy Lutomirski
If a process gets access to a mount from a different user
namespace, that process should not be able to take advantage of
setuid files or selinux entrypoints from that filesystem. Prevent
this by treating mounts from other mount namespaces and those not
owned by current_use
Hi!
> > > > When dropping the add_disk_randomness function in the legacy
> > > > /dev/random, I
> > > > would assume that without changes to add_input_randomness and
> > > > add_interrupt_randomness, we become even more entropy-starved.
> > >
> > > Sure, but your system isn't doing anything magic
= 0
> > RCU used illegally from extended quiescent state!
> > no locks held by swapper/1/0.
> >
> > stack backtrace:
> > CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.6.0-rc5-next-20160426+ #1113
> > Hardware name: Generic OMAP4 (Flattened Device Tree)
> > []
On Tue 2016-04-26 12:05:48, Andy Lutomirski wrote:
> On Tue, Apr 26, 2016 at 12:00 PM, Pavel Machek wrote:
> > On Mon 2016-04-25 20:34:07, Jarkko Sakkinen wrote:
> >> Intel(R) SGX is a set of CPU instructions that can be used by
> >> applications to set aside private regions of code and data. The
another warning,
See below :)
Regards,
Tony
8< --
===
[ INFO: suspicious RCU usage. ]
4.6.0-rc5-next-20160426+ #1114 Not tainted
---
include/trace/events/clk.h:59 suspicious rcu_dereference_check() usage!
other info that
* Steven Rostedt [160426 12:18]:
> Time to play "Whack-a-Mole"(TM)
:)
> Signed-off-by: Steven Rostedt
> ---
> diff --git a/arch/arm/mach-omap2/powerdomain.c
> b/arch/arm/mach-omap2/powerdomain.c
> index 78af6d8cf2e2..12b66b5bcc55 100644
> --- a/arch/arm/mach-omap2/powerdomain.c
> +++ b/arch/ar
Expand the check in should_remove_suid() to keep privileges for
CAP_FSETID in s_user_ns rather than init_user_ns.
Signed-off-by: Seth Forshee
Acked-by: Serge Hallyn
---
fs/inode.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/inode.c b/fs/inode.c
index 69b8b526c194..c
The VPU clock is also the clock for our AXI bus, so we really can't
disable it. This might have happened during boot if, for example,
uart1 (aux_uart clock) probed and was then disabled before the other
consumers of the VPU clock had probed.
Signed-off-by: Eric Anholt
---
drivers/clk/bcm/clk-bc
On Tue, Apr 26, 2016 at 09:24:34PM +0200, Arnd Bergmann wrote:
> On Tuesday 26 April 2016 20:23:35 Andrew Lunn wrote:
> > > A more complex problem would be having a PHY driver for a device
> > > that can be either an ethernet phy or some other phy.
> >
> > I doubt that ever happens. You can have u
On 04/26/2016 02:55 AM, Joonsoo Kim wrote:
On Mon, Apr 25, 2016 at 03:35:50PM +0200, Vlastimil Babka wrote:
@@ -846,9 +845,11 @@ isolate_migratepages_block(struct compact_control *cc,
unsigned long low_pfn,
spin_unlock_irqrestore(&zone->lru_lock, flags);
If the firmware had set up a clock to source from PLLC, go along with
it. But if we're looking for a new parent, we don't want to switch it
to PLLC because the firmware will force PLLC (and thus the AXI bus
clock) to different frequencies during over-temp/under-voltage,
without notification to Lin
This commit adds an _rcuidle suffix to a pair of trace events to
prevent the following splat:
> ===
> [ INFO: suspicious RCU usage. ]
> 4.6.0-rc5-next-20160426+ #1114 Not tainted
> ---
> include
On 04/15/2016 11:07 AM, Mel Gorman wrote:
From: Vlastimil Babka
An important function for cpusets is cpuset_node_allowed(), which optimizes on
the fact if there's a single root CPU set, it must be trivially allowed. But
the check "nr_cpusets() <= 1" doesn't use the cpusets_enabled_key static ke
All current callers of in_userns pass current_user_ns as the
first argument. Simplify by replacing in_userns with
current_in_userns which checks whether current_user_ns is in the
namespace supplied as an argument.
Signed-off-by: Seth Forshee
Acked-by: James Morris
Acked-by: Serge Hallyn
---
fs
1 - 100 of 1589 matches
Mail list logo
