On Mon, Jan 20, 2014 at 09:37:14AM -0800, Marcel Holtmann wrote:
Hi Alexander,
all 4 patches have been applied to bluetooth-next tree.
Maybe a bit late, but I've just seen they miss a Cc: stable@vger.kernel.org
to automatically end up in 3.12 and 3.13 too.
we can always promote
Hi Gianluca,
all 4 patches have been applied to bluetooth-next tree.
Maybe a bit late, but I've just seen they miss a Cc: stable@vger.kernel.org
to automatically end up in 3.12 and 3.13 too.
we can always promote them to stable. On Purpose I wanted them to cycle
through bluetooth-next
This patch fix the below crash
NIP [c004cee4] .__hash_page_thp+0x2a4/0x440
LR [c00439ac] .hash_page+0x18c/0x5e0
...
Call Trace:
[c00736103c40] [1b00] 0x1b00(unreliable)
[437908.479693] [c00736103d50] [c00439ac] .hash_page+0x18c/0x5e0
This patch fix the below crash
NIP [c004cee4] .__hash_page_thp+0x2a4/0x440
LR [c00439ac] .hash_page+0x18c/0x5e0
...
Call Trace:
[c00736103c40] [1b00] 0x1b00(unreliable)
[437908.479693] [c00736103d50] [c00439ac] .hash_page+0x18c/0x5e0
This patch fix the below crash
NIP [c004cee4] .__hash_page_thp+0x2a4/0x440
LR [c00439ac] .hash_page+0x18c/0x5e0
...
Call Trace:
[c00736103c40] [1b00] 0x1b00(unreliable)
[437908.479693] [c00736103d50] [c00439ac] .hash_page+0x18c/0x5e0
From: Li Zhong zh...@linux.vnet.ibm.com
It seems that forward declaration couldn't work well with typedef, use
struct spinlock directly to avoiding following build errors:
In file included from include/linux/spinlock.h:81,
from include/linux/seqlock.h:35,
from
From: Sujith Manoharan c_man...@qca.qualcomm.com
Currently, when a station leaves an IBSS network, the
corresponding BSS is not dropped from cfg80211 if there are
other active stations in the network. But, the small
window that is present when trying to determine a station's
status based
When cgroup_mount() fails to allocate an id for the root, it didn't
set ret before jumping to unlock_drop ending up returning 0 after a
failure. Fix it.
Signed-off-by: Tejun Heo t...@kernel.org
Cc: stable@vger.kernel.org
---
kernel/cgroup.c | 6 +++---
1 file changed, 3 insertions(+), 3
cgroup_cfts_commit() walks the cgroup hierarchy that the target
subsystem is attached to and tries to apply the file changes. Due to
the convolution with inode locking, it can't keep cgroup_mutex locked
while iterating. It currently holds only RCU read lock around the
actual iteration and then
cgroup_create() was returning 0 after allocation failures. Fix it.
Signed-off-by: Tejun Heo t...@kernel.org
Cc: stable@vger.kernel.org
---
kernel/cgroup.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/kernel/cgroup.c b/kernel/cgroup.c
index 364aeb22..2e9f12a
On 01/27/2014 07:02 PM, Guillaume Morin wrote:
On 27 Jan 16:28, Greg KH wrote:
I have verified commit 27c73ae759774e63313c1fbfeb17ba076cea64c5 indeed
fixes this bug. I have backported this fix to 3.4. I will run some more
tests and then I can send it out for 3.4 stable. Patch from upstream
Backport from upstream commit 27c73ae759774e63313c1fbfeb17ba076cea64c5
Commit 7cb2ef56e6a8 (mm: fix aio performance regression for database
caused by THP) can cause dereference of a dangling pointer if
split_huge_page runs during PageHuge() if there are updates to the
tail_page-private field.
The changes in patch 1431574a1c4c (lib/decompressors: fix no limit
output buffer length) avoid doing decompression a byte at a time when
decompressing into high physical addresses using a small, well isolated
change. The patch can give a very noticable improvement in kernel boot
times on affected
On Tue, Jan 28, 2014 at 09:04:59AM -0700, Khalid Aziz wrote:
On 01/27/2014 07:02 PM, Guillaume Morin wrote:
On 27 Jan 16:28, Greg KH wrote:
I have verified commit 27c73ae759774e63313c1fbfeb17ba076cea64c5 indeed
fixes this bug. I have backported this fix to 3.4. I will run some more
tests
On 28 Jan 8:27, Greg KH wrote:
I just sent out backported patch for 3.4. I also verified the upstream
commit does apply to stable 3.10 and 3.12 without any changes which
Guillaume has verified as well.
Thanks so much, I'll queue this up in a few days.
I have tested a 3.4.77 kernel
On Tue, Jan 28, 2014 at 04:14:28PM +, Mark Brown wrote:
The changes in patch 1431574a1c4c (lib/decompressors: fix no limit
output buffer length) avoid doing decompression a byte at a time when
decompressing into high physical addresses using a small, well isolated
change. The patch can
On 01/27/2014 01:17 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.13.1 release.
There are 10 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
Subject: [merged] compat-fix-sys_fanotify_mark.patch removed from -mm tree
To:
Subject: + vsprintf-ignore-arguments-to-%n.patch added to -mm tree
To:
keesc...@chromium.org,dbork...@redhat.com,jkos...@suse.cz,j...@perches.com,o...@lixom.net,rmal...@gmail.com,stable@vger.kernel.org,step...@codeaurora.org,v...@zeniv.linux.org.uk
From: a...@linux-foundation.org
Date: Tue, 28
Subject: + mm-mempolicyc-fix-mempolicy-printing-in-numa_maps.patch added to -mm
tree
To:
rient...@google.com,mgor...@suse.de,mi...@kernel.org,pet...@infradead.org,rlipp...@google.com,stable@vger.kernel.org
From: a...@linux-foundation.org
Date: Tue, 28 Jan 2014 12:08:39 -0800
The patch titled
It's in my git tree here:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=afs
David
--
To unsubscribe from this list: send the line unsubscribe stable in
the body of a message to majord...@vger.kernel.org
More majordomo info at
From: Pali Rohár pali.ro...@gmail.com
Subject: afs: proc cells and rootcell are writeable
Both proc files are writeable and used for configuring cells. But
there is missing correct mode flag for writeable files.
Without this patch it is not possible to write to cells and rootcell files
which
On Tue, 28 Jan 2014 20:08:30 + David Howells dhowe...@redhat.com wrote:
It's in my git tree here:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=afs
Well OK, but that patch (which you first merged on Dec 17!) is not yet
in linux-next, so as far as
At Red Hat we base our real-time kernel off of 3.10.27 and do lots of
stress testing on that kernel. This has discovered some bugs that we
can hit with the vanilla 3.10.27 kernel (no -rt patches applied).
I sent out a bug fix that can cause a crash with the current 3.10.27
when you add and then
From: Steven Rostedt (Red Hat) rost...@goodmis.org
The backport of upstream commit 205983c43700ac3 (sit: allow to use rtnl
ops on fb tunnel) had a dependency on commit 5e6700b3bf98 (sit: add
support of x-netns). The dependency was on the way that commit
unregistered the sit devices.
Since the
From: Willem de Bruijn will...@google.com
[ Upstream commit 9434266f2c645d4fcf62a03a8e36ad8075e37943 ]
Bug: The fallback device is created in sit_init_net and assumed to be
freed in sit_exit_net. First, it is dereferenced in that function, in
sit_destroy_tunnels:
struct net *net =
Subject: [to-be-updated] vsprintf-ignore-arguments-to-%n.patch removed from -mm
tree
To:
keesc...@chromium.org,dbork...@redhat.com,jkos...@suse.cz,j...@perches.com,o...@lixom.net,rmal...@gmail.com,stable@vger.kernel.org,step...@codeaurora.org,v...@zeniv.linux.org.uk,mm-comm...@vger.kernel.org
Hello,
I'd like to nominate
5d2f4767c4eacab351b8450b0de4d3261fe1a957 (drm/nouveau/bios: fix
offset calculation for BMPv1 bioses)
for inclusion into the linux-stable trees. This should avoid a VBIOS
parsing/execution error for some very old Riva TNT cards. The bug
reporter was finally able to
On 2014/1/28 23:32, Tejun Heo wrote:
When cgroup_mount() fails to allocate an id for the root, it didn't
set ret before jumping to unlock_drop ending up returning 0 after a
failure. Fix it.
Signed-off-by: Tejun Heo t...@kernel.org
Cc: stable@vger.kernel.org
Acked-by: Li Zefan
On 2014/1/28 23:32, Tejun Heo wrote:
cgroup_cfts_commit() walks the cgroup hierarchy that the target
subsystem is attached to and tries to apply the file changes. Due to
the convolution with inode locking, it can't keep cgroup_mutex locked
while iterating. It currently holds only RCU read
On 2014/1/28 23:32, Tejun Heo wrote:
cgroup_create() was returning 0 after allocation failures. Fix it.
Signed-off-by: Tejun Heo t...@kernel.org
Cc: stable@vger.kernel.org
Acked-by: Li Zefan lize...@huawei.com
--
To unsubscribe from this list: send the line unsubscribe stable in
the body of
From: Steven Rostedt rost...@goodmis.org
Date: Tue, 28 Jan 2014 15:57:56 -0500
At Red Hat we base our real-time kernel off of 3.10.27 and do lots of
stress testing on that kernel. This has discovered some bugs that we
can hit with the vanilla 3.10.27 kernel (no -rt patches applied).
I sent
32 matches
Mail list logo
