* John Stultz john.stu...@linaro.org wrote:
Just wanted to send out a few timekeeping fixes that were merged
in 3.14 which are appropriate for -stable.
No, they are not appropriate at all.
This queue backports the following fixes:
-
The version of isci driver has not been updated for 2 years.
It was 83 isci commits ago. Suspend/resume support has been implemented
and many bugs have been fixed since 1.1. Now update the version to 1.2.
Signed-off-by: Lukasz Dorau lukasz.do...@intel.com
Cc: stable@vger.kernel.org
---
On Thursday, January 23, 2014 10:39 AM Lukasz Dorau lukasz.do...@intel.com
wrote:
The version of isci driver has not been updated for 2 years.
It was 83 isci commits ago. Suspend/resume support has been implemented
and many bugs have been fixed since 1.1. Now update the version to 1.2.
On Wed, Jan 22, 2014 at 12:01:23PM +, Steven Whitehouse wrote:
This is for 3.13-stable, 3.12-stable and 3.10-stable. It is upstream:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/gfs2/inode.c?id=62e96cf81988101fe9e086b2877307b6adda5197
Steve.
Thanks Steven, I'm
From: Ville Syrjälä ville.syrj...@linux.intel.com
commit 7ad228b11ec26a820291c9f5a1168d6176580dc1 upstream.
When the pipe A force quirk is applied the code will attempt to grab
a crtc mutex during intel_modeset_setup_hw_state(). If we're already
holding all crtc mutexes this will obviously
sdata-u.ap.request_smps_work can’t be flushed synchronously
under wdev_lock(wdev) since ieee80211_request_smps_ap_work
itself locks the same lock.
While at it, reset the driver_smps_mode when the ap is
stopped to its default: OFF.
This solves:
On Thu, 2014-01-23 at 14:28 +0200, Emmanuel Grumbach wrote:
sdata-u.ap.request_smps_work can’t be flushed synchronously
under wdev_lock(wdev) since ieee80211_request_smps_ap_work
itself locks the same lock.
Applied.
johannes
--
To unsubscribe from this list: send the line unsubscribe stable
On 01/23/2014 02:13 AM, Sarah Sharp wrote:
If it really matters that a driver be able to get an immediate -EPIPE
response back from a device when the endpoint is halted, I can rip the
code out of xhci_endpoint_reset() and make the driver manually clean up
the ring at the time of the stall, like
On Thu, Jan 23, 2014 at 01:12:20PM +0800, Wang Nan wrote:
Hi Greg,
b25f3e1c358434bf850220e04f28eebfc45eb634
ARM: 7938/1: OMAP4/highbank: Flush L2 cache before disabling
This patch looks applicable to stable-3.10, which flush outer cache before
soft_restart(). Without this patch, kexec on
This is a note to let you know that I've just added the patch titled
ARM: 7938/1: OMAP4/highbank: Flush L2 cache before disabling
to the 3.12-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch
This is a note to let you know that I've just added the patch titled
drm/i915: Don't grab crtc mutexes in intel_modeset_gem_init()
to the 3.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch
This is a note to let you know that I've just added the patch titled
ARM: 7938/1: OMAP4/highbank: Flush L2 cache before disabling
to the 3.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch
This is a note to let you know that I've just added the patch titled
drm/i915: Don't grab crtc mutexes in intel_modeset_gem_init()
to the 3.12-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch
This is a note to let you know that I've just added the patch titled
staging: wlags49_h2: buffer overflow setting station name
to the 3.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
On 01/23/2014 01:17 AM, Ingo Molnar wrote:
* John Stultz john.stu...@linaro.org wrote:
Just wanted to send out a few timekeeping fixes that were merged
in 3.14 which are appropriate for -stable.
No, they are not appropriate at all.
This queue backports the following fixes:
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt rost...@goodmis.org
commit 1739f09e33d8f66bf48ddbc3eca615574da6c4f6 upstream.
Function tracing callbacks expect to have the ftrace_ops that registered it
passed to them, not the
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Taras Kondratiuk taras.kondrat...@linaro.org
commit b25f3e1c358434bf850220e04f28eebfc45eb634 upstream.
Kexec disables outer cache before jumping to reboot code, but it doesn't
flush it
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown ne...@suse.de
commit 8313b8e57f55b15e5b7f7fc5d1630bbf686a9a97 upstream.
If an array is started degraded, and then the missing device
is found it can be re-added and a minimal
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown ne...@suse.de
commit b50c259e25d9260b9108dc0c2964c26e5ecbe1c1 upstream.
If we discover a bad block when reading we split the request and
potentially read some of it from a different
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Jon Medhurst t...@linaro.org
commit fe43390702a1b5741fdf217063b05c7612b38303 upstream.
When the pl011 is being used for a console, pl011_console_write forces
the control register (CR) to
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown ne...@suse.de
commit 1cc03eb93245e63b0b7a7832165efdc52e25b4e6 upstream.
commit 5d8c71f9e5fbdd95650be00294d238e27a363b5c
md: raid5 crash during degradation
Fixed a crash in an
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Paulo Zanoni paulo.r.zan...@intel.com
commit 0882dae983707455e97479e5e904e37673517ebc upstream.
Properly zero the refcounts and crtc-ddi_pll_set so the previous HW
state doesn't affect the
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown ne...@suse.de
commit e8b849158508565e0cd6bc80061124afc5879160 upstream.
commit e875ecea266a543e643b19e44cf472f1412708f9
md/raid10 record bad blocks as needed during recovery.
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Geert Uytterhoeven ge...@linux-m68k.org
commit f92f455f67fef27929e6043499414605b0c94872 upstream.
{,set}page_address() are macros if WANT_PAGE_VIRTUAL. If
!WANT_PAGE_VIRTUAL, they're plain C
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Andreas Rohner andreas.roh...@gmx.net
commit 70f2fe3a26248724d8a5019681a869abdaf3e89a upstream.
There is a bug in the function nilfs_segctor_collect, which results in
active data being written
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins hu...@google.com
commit eecc1e426d681351a6026a7d3e7d225f38955b6c upstream.
We see General Protection Fault on RSI in copy_page_rep: that RSI is
what you get from a NULL struct
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: H Hartley Sweeten hswee...@visionengravers.com
commit 48108fe3daa0d142f9b97178fdb23704ea3a407b upstream.
The dev-irq passed to request_irq() will always be 0 when the auto_attach
function is
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Robert Richter r...@kernel.org
commit bee09ed91cacdbffdbcd3b05de8409c77ec9fcd6 upstream.
On AMD family 10h we see following error messages while waking up from
S3 for all non-boot CPUs leading
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Jean Delvare kh...@linux-fr.org
commit 3f9aec7610b39521c7c69d754de7265f6994c194 upstream.
When the core number exceeds 9, the size of the buffer storing the
alarm attribute name is
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Eric W. Biederman ebied...@xmission.com
commit f48cfddc6729ef133933062320039808bafa6f45 upstream.
Aditya Kali (adityak...@google.com) wrote:
Commit bf056bfa80596a5d14b26b17276a56a0dcb080e5:
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt rost...@goodmis.org
commit 3dc91d4338d698ce77832985f9cb183d8eeaf6be upstream.
While running stress tests on adding and deleting ftrace instances I hit
this bug:
BUG: unable
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Bob Peterson rpete...@redhat.com
commit 62e96cf81988101fe9e086b2877307b6adda5197 upstream.
This patch calls get_write_access in function gfs2_setattr_chown,
which merely increases
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Jianguo Wu wujian...@huawei.com
commit a49ecbcd7b0d5a1cda7d60e03df402dd0ef76ac8 upstream.
After a successful hugetlb page migration by soft offline, the source
page will either be freed into
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Vijaya Kumar K vijay.kil...@gmail.com
commit 4f9b4fb7a2091eec339413a460b1665758401828 upstream.
In case of normal kexec kernel load, all cpu's are offlined
before calling machine_kexec().But
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara j...@suse.cz
commit f9b0e058cbd04ada76b13afffa7e1df830543c24 upstream.
Commit 4f8ad655dbc8 writeback: Refactor writeback_single_inode() added
a condition to skip clean inode. However
This is the start of the stable review cycle for the 3.10.28 release.
There are 23 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 made by Sat Jan 25 18:38:43 UTC 2014.
Anything
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: H Hartley Sweeten hswee...@visionengravers.com
commit 90daf69a7a3f1d1a41018c799968a0bb896d65e0 upstream.
The SDF_CMD_READ should be one of the s-subdev_flags not part of
the s-type.
I originally reported this on 3.4.76 but I see the same issue on 3.4.77.
I've also tested with a 3.13 rc and could not reproduce the issue. All
of these tests are done on a 12-core amd64 machines.
I wrote this simple program (attached) to play around with kernel AIO.
It simply does kernel AIO
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: H Hartley Sweeten hswee...@visionengravers.com
commit 48108fe3daa0d142f9b97178fdb23704ea3a407b upstream.
The dev-irq passed to request_irq() will always be 0 when the auto_attach
function is
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Eric W. Biederman ebied...@xmission.com
commit f48cfddc6729ef133933062320039808bafa6f45 upstream.
Aditya Kali (adityak...@google.com) wrote:
Commit bf056bfa80596a5d14b26b17276a56a0dcb080e5:
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
commit 2b844ba79f4a114bd228ad6fee040ffd99a0963d upstream.
This reverts commit f6308b36c411 (ACPI: Add BayTrail SoC GPIO and LPSS
ACPI IDs), because
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Andreas Rohner andreas.roh...@gmx.net
commit 70f2fe3a26248724d8a5019681a869abdaf3e89a upstream.
There is a bug in the function nilfs_segctor_collect, which results in
active data being written
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Paulo Zanoni paulo.r.zan...@intel.com
commit 0882dae983707455e97479e5e904e37673517ebc upstream.
Properly zero the refcounts and crtc-ddi_pll_set so the previous HW
state doesn't affect the
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Sudeep Holla sudeep.ho...@arm.com
commit e44ef891e9e68b6ce7d3fd3bac73b7d5433050ae upstream.
The MPIDR contains specific bitfields(MPIDR.Aff{2..0}) which uniquely
identify a CPU, in addition to
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Eric W. Biederman ebied...@xmission.com
commit 41301ae78a99ead04ea42672a1ab72c6f44cc81d upstream.
Gao feng gaof...@cn.fujitsu.com reported that commit
e51db73532955dc5eaba4235e62b74b460709d5b
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Qais Yousef qais.you...@imgtec.com
commit 5a610fcc7390ee60308deaf09426ada87a1eeec2 upstream.
In file included from kernel/crash_dump.c:2:0:
include/linux/crash_dump.h:22:27: error: unknown
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Robert Richter r...@kernel.org
commit bee09ed91cacdbffdbcd3b05de8409c77ec9fcd6 upstream.
On AMD family 10h we see following error messages while waking up from
S3 for all non-boot CPUs leading
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt rost...@goodmis.org
commit 1739f09e33d8f66bf48ddbc3eca615574da6c4f6 upstream.
Function tracing callbacks expect to have the ftrace_ops that registered it
passed to them, not the
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt rost...@goodmis.org
commit 3dc91d4338d698ce77832985f9cb183d8eeaf6be upstream.
While running stress tests on adding and deleting ftrace instances I hit
this bug:
BUG: unable
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Eric W. Biederman ebied...@xmission.com
commit 1f7f4dde5c945f41a7abc2285be43d918029ecc5 upstream.
Serge Hallyn serge.hal...@ubuntu.com writes:
Hi Oleg,
commit
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Stephen Warren swar...@nvidia.com
commit 2fac2b891f287691c27ee8d2eeecf39571b27fea upstream.
The body of i2c_parent_is_i2c_adapter() is currently guarded by
I2C_MUX. It should be CONFIG_I2C_MUX
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara j...@suse.cz
commit f9b0e058cbd04ada76b13afffa7e1df830543c24 upstream.
Commit 4f8ad655dbc8 writeback: Refactor writeback_single_inode() added
a condition to skip clean inode. However
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Jon Medhurst t...@linaro.org
commit fe43390702a1b5741fdf217063b05c7612b38303 upstream.
When the pl011 is being used for a console, pl011_console_write forces
the control register (CR) to
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Taras Kondratiuk taras.kondrat...@linaro.org
commit b25f3e1c358434bf850220e04f28eebfc45eb634 upstream.
Kexec disables outer cache before jumping to reboot code, but it doesn't
flush it
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: H Hartley Sweeten hswee...@visionengravers.com
commit 90daf69a7a3f1d1a41018c799968a0bb896d65e0 upstream.
The SDF_CMD_READ should be one of the s-subdev_flags not part of
the s-type.
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka mpato...@redhat.com
commit 03e5ac2fc3bf6f4140db0371e8bb4243b24e3e02 upstream.
Commit 8456a648cf44 (slab: use struct page for slab management) causes
a crash in the LVM2
This is the start of the stable review cycle for the 3.12.9 release.
There are 27 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 made by Sat Jan 25 19:06:36 UTC 2014.
Anything
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Jean Delvare kh...@linux-fr.org
commit 3f9aec7610b39521c7c69d754de7265f6994c194 upstream.
When the core number exceeds 9, the size of the buffer storing the
alarm attribute name is
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Bob Peterson rpete...@redhat.com
commit 62e96cf81988101fe9e086b2877307b6adda5197 upstream.
This patch calls get_write_access in function gfs2_setattr_chown,
which merely increases
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown ne...@suse.de
commit e8b849158508565e0cd6bc80061124afc5879160 upstream.
commit e875ecea266a543e643b19e44cf472f1412708f9
md/raid10 record bad blocks as needed during recovery.
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown ne...@suse.de
commit 1cc03eb93245e63b0b7a7832165efdc52e25b4e6 upstream.
commit 5d8c71f9e5fbdd95650be00294d238e27a363b5c
md: raid5 crash during degradation
Fixed a crash in an
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown ne...@suse.de
commit b50c259e25d9260b9108dc0c2964c26e5ecbe1c1 upstream.
If we discover a bad block when reading we split the request and
potentially read some of it from a different
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Hugh Dickins hu...@google.com
commit eecc1e426d681351a6026a7d3e7d225f38955b6c upstream.
We see General Protection Fault on RSI in copy_page_rep: that RSI is
what you get from a NULL struct
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Geert Uytterhoeven ge...@linux-m68k.org
commit f92f455f67fef27929e6043499414605b0c94872 upstream.
{,set}page_address() are macros if WANT_PAGE_VIRTUAL. If
!WANT_PAGE_VIRTUAL, they're plain C
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown ne...@suse.de
commit 8313b8e57f55b15e5b7f7fc5d1630bbf686a9a97 upstream.
If an array is started degraded, and then the missing device
is found it can be re-added and a minimal
On Wed, 22 Jan 2014, Wang Nan wrote:
This patch allows the kernel to be loaded at the middle of kernel awared
physical memory. Before this patch, users must use mem= or device tree to
cheat
kernel about the start address of physical memory.
This feature is useful in some special cases,
On Thu, Jan 23, 2014 at 02:15:07PM -0500, Nicolas Pitre wrote:
On Wed, 22 Jan 2014, Wang Nan wrote:
This patch allows the kernel to be loaded at the middle of kernel awared
physical memory. Before this patch, users must use mem= or device tree to
cheat
kernel about the start address of
Added the functions task_ppid_nr_ns() and task_ppid_nr() to abstract the lookup
of the PPID (real_parent's pid_t) of a process, including rcu locking, in the
arbitrary and init_pid_ns.
This provides an alternative to sys_getppid(), which is relative to the child
process' pid namespace.
(informed
On Thu, Jan 23, 2014 at 07:55:14PM +0100, Guillaume Morin wrote:
I originally reported this on 3.4.76 but I see the same issue on 3.4.77.
I've also tested with a 3.13 rc and could not reproduce the issue. All
of these tests are done on a 12-core amd64 machines.
I wrote this simple program
On Thu, Jan 23, 2014 at 07:55:14PM +0100, Guillaume Morin wrote:
I originally reported this on 3.4.76 but I see the same issue on 3.4.77.
I've also tested with a 3.13 rc and could not reproduce the issue. All
of these tests are done on a 12-core amd64 machines.
I wrote this simple program
On 01/23/2014 12:38 PM, Greg KH wrote:
On Thu, Jan 23, 2014 at 07:55:14PM +0100, Guillaume Morin wrote:
I originally reported this on 3.4.76 but I see the same issue on 3.4.77.
I've also tested with a 3.13 rc and could not reproduce the issue. All
of these tests are done on a 12-core amd64
On Thu, 23 Jan 2014, Russell King - ARM Linux wrote:
On Thu, Jan 23, 2014 at 02:15:07PM -0500, Nicolas Pitre wrote:
On Wed, 22 Jan 2014, Wang Nan wrote:
This patch allows the kernel to be loaded at the middle of kernel awared
physical memory. Before this patch, users must use mem= or
On 23 Jan 11:38, Greg KH wrote:
Please at least email the people involved in the patch, as the only real
subscribers to the stable mailing list are the people who make the
stable releases, not the developers who write the patches that are
backported.
Sorry, will do in the future.
Then it
Khalid,
On 23 Jan 12:58, Khalid Aziz wrote:
This does look like the same issue that is fixed with commit
27c73ae759774e63313c1fbfeb17ba076cea64c5. I will build a 3.4.69
kernel and try to reproduce this problem.
Thanks. You should be able to reproduce the issue with any stable 3.4
kernels
On Thu, Jan 23, 2014 at 09:31:26PM +0100, Guillaume Morin wrote:
On 23 Jan 11:38, Greg KH wrote:
Please at least email the people involved in the patch, as the only real
subscribers to the stable mailing list are the people who make the
stable releases, not the developers who write the
Subject: + mm-ignore-vm_softdirty-on-vma-merging.patch added to -mm tree
To:
gorcu...@gmail.com,gn...@rvzt.net,gorcu...@openvz.org,mgor...@suse.de,stable@vger.kernel.org,xe...@parallels.com
From: a...@linux-foundation.org
Date: Thu, 23 Jan 2014 13:01:33 -0800
The patch titled
Subject: mm:
Subject: +
lib-genallocc-add-check-gen_pool_dma_alloc-if-dma-pointer-is-not-null.patch
added to -mm tree
To:
prabhakar.cse...@gmail.com,b42...@freescale.com,j...@perches.com,p.za...@pengutronix.de,sachin.ka...@linaro.org,stable@vger.kernel.org
From: a...@linux-foundation.org
Date: Thu, 23 Jan
On 23 Jan 12:48, Greg KH wrote:
That's not good, so I'm guessing 3.10 is also affected, which is going
to cause people worries...
Sorry to be the bearer of bad news. Do you want me to give 3.10.27 a
quick shot?
--
Guillaume Morin guilla...@morinfr.org
--
To unsubscribe from this list: send
On Thu, Jan 23, 2014 at 11:06:29PM +0100, Guillaume Morin wrote:
On 23 Jan 12:48, Greg KH wrote:
That's not good, so I'm guessing 3.10 is also affected, which is going
to cause people worries...
Sorry to be the bearer of bad news. Do you want me to give 3.10.27 a
quick shot?
Sure, that
On Thu, Jan 23, 2014 at 11:06:37AM -0800, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.12.9 release.
There are 27 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.
On Thu, Jan 23, 2014 at 10:39:33AM -0800, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.28 release.
There are 23 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.
From: Vlastimil Babka vba...@suse.cz
Subject: mm: munlock: fix potential race with THP page split
Since commit ff6a6da60 (mm: accelerate munlock() treatment of THP pages)
munlock skips tail pages of a munlocked THP page. There is some attempt
to prevent bad consequences of racing with a THP page
From: Michal Hocko mho...@suse.cz
Subject: memcg: fix endless loop caused by mem_cgroup_iter
Hugh has reported an endless loop when the hardlimit reclaim sees the same
group all the time. This might happen when the reclaim races with the
memcg removal.
shrink_zone
From: Cyrill Gorcunov gorcu...@gmail.com
Subject: mm: ignore VM_SOFTDIRTY on VMA merging
The VM_SOFTDIRTY bit affects vma merge routine: if two VMAs has all bits
in vm_flags matched except dirty bit the kernel can't longer merge them
and this forces the kernel to generate new VMAs instead.
It
From: Michal Hocko mho...@suse.cz
Subject: memcg: fix css reference leak and endless loop in mem_cgroup_iter
19f39402864e (memcg: simplify mem_cgroup_iter) has reorganized
mem_cgroup_iter code in order to simplify it. A part of that change was
dropping an optimization which didn't call
From: Naoya Horiguchi n-horigu...@ah.jp.nec.com
Subject: mm/memory-failure.c: shift page lock from head page to tail page after
thp split
After thp split in hwpoison_user_mappings(), we hold page lock on the raw
error page only between try_to_unmap, hence we are in danger of race condition.
I
From: Hugh Dickins hu...@google.com
Subject: mm/memcg: iteration skip memcgs not yet fully initialized
It is surprising that the mem_cgroup iterator can return memcgs which have
not yet been fully initialized. By accident (or trial and error?) this
appears not to present an actual problem; but
From: Stephen Warren swar...@nvidia.com
Subject: rtc: max8907: weekday encoding fixes
The current MAX8907 driver has two issues related to weekday value
handling:
1)
The HW WEEKDAY register has range 0..6 rather than 1..7 as documented.
Note that I validated the actual HW range by observing
On 01/23/2014 01:38 PM, Guillaume Morin wrote:
Khalid,
On 23 Jan 12:58, Khalid Aziz wrote:
This does look like the same issue that is fixed with commit
27c73ae759774e63313c1fbfeb17ba076cea64c5. I will build a 3.4.69
kernel and try to reproduce this problem.
Thanks. You should be able to
On 23 Jan 14:11, Greg KH wrote:
Sorry to be the bearer of bad news. Do you want me to give 3.10.27 a
quick shot?
Sure, that would be great to know.
Yes, I can reproduce it as well with 3.10.27
--
Guillaume Morin guilla...@morinfr.org
--
To unsubscribe from this list: send the line
On Thu, Jan 23, 2014 at 03:20:30PM -0800, Guenter Roeck wrote:
On Thu, Jan 23, 2014 at 11:06:37AM -0800, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.12.9 release.
There are 27 patches in this series, all will be posted as a response
to this one. If
On Thu, Jan 23, 2014 at 03:35:45PM -0800, Guenter Roeck wrote:
On Thu, Jan 23, 2014 at 10:39:33AM -0800, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.28 release.
There are 23 patches in this series, all will be posted as a response
to this one. If
On 01/23/2014 08:11 PM, Greg Kroah-Hartman wrote:
On Thu, Jan 23, 2014 at 03:20:30PM -0800, Guenter Roeck wrote:
On Thu, Jan 23, 2014 at 11:06:37AM -0800, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.12.9 release.
There are 27 patches in this series, all
93 matches
Mail list logo
