On 2014/9/9 4:25, Guenter Roeck wrote:
> Hi,
>
> Please apply the following patch to the 3.2 and 3.4 kernels to fix a
> compile error seen when using a new (or1k) toolchain for openrisc builds.
>
> 160d837 ('openrisc: add missing header inclusion')
>
Applied to 3.4. Thanks.
--
To unsubscribe f
On 2014/8/26 1:33, Paul Gortmaker wrote:
> commit 7400ce7ee9595432b2a1402b6ffcac9faf38d9ae (v3.4.92-76-g7400ce7ee959)
> was a backport of commit ebebd49a8eab5e9aa1b1f8f1614ccc3c2120f886 upstream
> ("8250/16?50: Add support for Broadcom TruManage redirected serial port")
>
> However, in the context
On 2014/9/11 9:04, Ben Hutchings wrote:
> On Tue, 2014-08-05 at 16:20 -0700, Jay Vosburgh wrote:
>> Please consider commit
>>
>> commit e7b691b085fda913830e5280ae6f724b2a63c824
>> Author: Andi Kleen
>> Date: Sat Jun 9 02:40:03 2012 -0700
>>
>> slab/mempolicy: always use local policy fro
On 2014/8/16 0:06, Guenter Roeck wrote:
> Ben,
> Greg,
>
> please apply the following patches to the respective -stable branches.
>
> I started seeing the problems fixed with those patches after updating
> my qemu tests to also execute SMP builds. Patches apply cleanly to all
> branches, and my t
I've already sent these to stable mailing list.
On 2014/9/12 10:22, Wang Nan wrote:
> Hi Greg,
>
> Upstream commit 0c740d0afc3bff0a097ad03a1c8df92757516f5c and
> 1da4db0cd5c8a31d4468ec906b413e75e604b465 looks ignored by 3.10 (they are
> included by 3.12.22). Without these patches we meet real dea
On 2014/9/5 21:58, Guenter Roeck wrote:
> On 09/05/2014 12:55 AM, Li Zefan wrote:
>>>>> Li,
>>>>>
>>>>> it would be great if you can send me information about your -stable queue,
>>>>> ie how you maintain it and where it is located.
>>> Li,
>>>
>>> it would be great if you can send me information about your -stable queue,
>>> ie how you maintain it and where it is located. This will enable me to
>>> continue testing the stable queue for the 3.4 kernel.
>>>
>>
>> Thanks for testing LTS kernels!
>>
>> This is my 3.4.y git tree:
On 2014/9/4 15:12, Li Zefan wrote:
> Cc: Zhang Zhen
>
> On 2014/9/4 7:29, Greg KH wrote:
>> On Wed, Sep 03, 2014 at 04:25:30PM -0700, Greg KH wrote:
>>> On Wed, Sep 03, 2014 at 04:01:22PM -0700, David Rientjes wrote:
>>>> On Wed, 3 Sep 2014, gre...@linuxfounda
Hi Guenter,
Sorry for my late reply.
On 2014/8/27 12:59, Guenter Roeck wrote:
> On Tue, Aug 26, 2014 at 04:08:58PM -0700, Greg KH wrote:
>> Li has agreed to continue to support the 3.4 stable kernel tree until
>> September 2016. Update the releases.html page on kernel.org to reflect
>> this.
>>
Cc: Zhang Zhen
On 2014/9/4 7:29, Greg KH wrote:
> On Wed, Sep 03, 2014 at 04:25:30PM -0700, Greg KH wrote:
>> On Wed, Sep 03, 2014 at 04:01:22PM -0700, David Rientjes wrote:
>>> On Wed, 3 Sep 2014, gre...@linuxfoundation.org wrote:
>>>
The patch below does not apply to the 3.10-stable t
to get both the superblock refcnt and cgroup_root refcnt,
because cgroup_root may have no superblock assosiated with it.
- adjust/add comments.
tj: Updated comments. Renamed @sb to @pinned_sb.
Signed-off-by: Li Zefan
Signed-off-by: Tejun Heo
[lizf: Backported to 3.15:
- Adjust context
- s/per
_block and chain it at
kernfs_root->supers.
Signed-off-by: Tejun Heo
Signed-off-by: Greg Kroah-Hartman
[lizf: Backported to 3.15: Adjust context]
Signed-off-by: Li Zefan
---
fs/kernfs/dir.c | 1 +
fs/kernfs/kernfs-internal.h | 5 +
fs/kernfs/mount.c | 11 +++
. ]
Acked-by: Greg Kroah-Hartman
Signed-off-by: Li Zefan
Signed-off-by: Tejun Heo
---
fs/kernfs/mount.c | 30 ++
include/linux/kernfs.h | 1 +
2 files changed, 31 insertions(+)
diff --git a/fs/kernfs/mount.c b/fs/kernfs/mount.c
index d171b98..f973ae9 100644
--- a
ucing
percpu_ref_alive(). (Tejun)
- adjust comment.
tj: Updated the comment a bit.
Signed-off-by: Li Zefan
Signed-off-by: Tejun Heo
[lizf: Backported to 3.15:
- s/percpu_ref_tryget_live/atomic_inc_not_zero/
- Use goto instead of calling restart_syscall()
- Add cgroup_tree_mutex]
---
k
the forker's task_struct is duplicated (which includes ->mems_allowed)
> and it races with an update to cpuset_being_rebound in update_tasks_nodemask()
> then the task's mems_allowed doesn't get updated. And the child task's
> mems_allowed can be wrong if the cpuset
On 2014/6/25 15:20, Wang Nan wrote:
> From: Tim Kryger
>
...
> upstream inclusion
> DTS: DTS2014060600056
> directory: cherry-pick
>
>
>
Please remove the above lines.
> commit 33acbb82695f84e9429c1f7fbdeb4588dea12ffa upstream
>
commit 33acbb82695f84
On 2014/6/21 5:01, Tejun Heo wrote:
> Hello, Li.
>
> Sorry about the long delay.
>
> On Tue, Jun 10, 2014 at 10:58:45AM +0800, Li Zefan wrote:
>> Yes, this is a long-standing issue. Besides the race you described, the child
>> task's mems_allowed can be wrong
On 2014/6/9 17:13, David Rientjes wrote:
> On Mon, 9 Jun 2014, Gu Zheng wrote:
>
>>> I think your patch addresses the problem that you're reporting but misses
>>> the larger problem with cpuset.mems rebinding on fork(). When the
>>> forker's task_struct is duplicated (which includes ->mems_allo
On 2014/6/5 11:16, Xiangyu Lu wrote:
> Hi Greg,
> I found this bugfix is not in the latest 3.10.y, please backport it.
> As for now, 3.10.y LTS would still be vulnerable to CVE-2014-2672.
>
Please add this line：
"From: Stanislaw Gruszka "
> [ Upstream commit 21f8aaee0c62708654988ce092838aa7df4
On 2014/4/10 10:30, Weng Meiling wrote:
> On 2014/4/10 7:37, Greg KH wrote:
>> On Wed, Mar 12, 2014 at 05:16:47PM +0800, Weng Meiling wrote:
>>> Hi Greg,
>>>
>>> We've started to analize the list of upstream commits that have been
>>> backported to 3.2 but missing from 3.4.
>>>
>>> For the 13 commi
On 2014/3/8 9:03, Greg KH wrote:
> On Fri, Feb 28, 2014 at 02:15:59PM +0800, Li Zefan wrote:
>> Hi Greg,
>>
>> We'll hold off remaining stable requests until you finish handling
>> those we've sent out.
>
> I should be caught up now, if not, please resen
Hi Greg,
We'll hold off remaining stable requests until you finish handling
those we've sent out.
On 2014/2/27 9:52, Jianguo Wu wrote:
> Hi Greg,
>
> These are a bunch of commits from the list of upstream commits
> that have been backported to 3.2 but missing from 3.4.
>
> For the 16 commits th
>> fs/jffs2/nodemgmt.c | 13 +
>> 1 file changed, 9 insertions(+), 4 deletions(-)
>>
>> diff -puN
>> fs/jffs2/nodemgmt.c~jffs2-avoid-soft-lockup-in-jffs2_reserve_space_gc
>> fs/jffs2/nodemgmt.c
>> --- a/fs/jffs2/nodemgmt.c~jffs2-avoid-soft-lockup-in-jffs2_reserve_space_gc
>> +++ a/
i);
continue;
}
spin_unlock(&testlock);
}
and the bug can be fixed by these two commits.
--
Li Zefan
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majord...@vger.kernel.org
More
>>> BTW, the right way to handle lock balancing is to handle the unlocking
>>> at the same level where you do the locking. So I guess you're looking
>>> for the following patch instead, which is really not very useful because
>>> (as Li noted) the lock is freed immediately afterward anyway:
>>>
>>
On 2014/2/19 8:15, Ben Hutchings wrote:
> On Tue, 2014-02-18 at 15:37 +0800, Li Zefan wrote:
>> Hi Greg,
>>
>> We've started to analize the list of upstream commits that have been
>> backported to 3.2 but missing from 3.4.
>>
>> For the 18 commits t
e its
argument.
Simplify it all and remove pageblock_default_order() altogether.
Reported-by: rajman mekaco
Cc: Mel Gorman
Cc: KAMEZAWA Hiroyuki
Cc: Tejun Heo
Cc: Minchan Kim
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
[lizf: Backported to 3.4: adjust context]
Signed-off-by: Li
EZAWA Hiroyuki
Cc: Benjamin Herrenschmidt
Cc: KOSAKI Motohiro
Cc: David Rientjes
Cc: Keping Chen
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
[lizf: Backported to 3.4: adjust context]
Signed-off-by: Li Zefan
---
mm/internal.h | 2 ++
mm/page_alloc.c | 4 ++--
mm/sparse.c
Hi Greg,
We've started to analize the list of upstream commits that have been
backported to 3.2 but missing from 3.4.
For the 18 commits that I've analized,
- 4 commits have been backported to 3.4. My script failed to detect them.
- 1 commit is obviosly not a bug fix, don't know why it went into
wed-by: Chris Wilson
Signed-off-by: Daniel Vetter
Signed-off-by: Dave Airlie
[lizf: Backported to 3.4: adjust context]
Signed-off-by: Li Zefan
---
drivers/gpu/drm/i915/i915_dma.c | 37 ++---
1 file changed, 30 insertions(+), 7 deletions(-)
diff --git a/drivers/gp
On 2014/2/13 14:48, Brian Norris wrote:
> Hi Li / Andrew,
>
> On Wed, Feb 12, 2014 at 12:44:55PM -0800, Andrew Morton wrote:
>> From: Li Zefan
>> Subject: jffs2: fix unbalanced locking
>>
>> This was found by our internal debugging feature on runtime, but this
On 2014/2/9 23:28, Ben Hutchings wrote:
> On Sat, 2014-02-08 at 12:15 +0800, Li Zefan wrote:
>> Hi Greg,
>>
>> I've gone through `git-log v3.4.. kernel/sched/rt.c`, and I believe those
>> commits
>> need to be backported to 3.4 stable.
>
> Are any of
ink:
http://lkml.kernel.org/r/1342508623-2887-1-git-send-email-ying@windriver.com
Signed-off-by: Ingo Molnar
[ lizf: backported to 3.4: adjust context ]
Signed-off-by: Li Zefan
---
include/linux/sched.h | 1 +
kernel/sched/rt.c | 6 +-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git
rnel.org/r/5fbf8e85ca34454794f0f7ecba79798f379d364...@hqmail04.nvidia.com
Signed-off-by: Ingo Molnar
[ lizf: backported to 3.4: adjust context ]
Signed-off-by: Li Zefan
---
kernel/sched/core.c | 3 ---
kernel/sched/fair.c | 7 +--
kernel/sched/rt.c| 1 +
kernel/sched/sched.h | 1 -
4 files
Hi Greg,
I've gone through `git-log v3.4.. kernel/sched/rt.c`, and I believe those
commits
need to be backported to 3.4 stable.
454c7f7eaedcdf4c15c449e43902980cbdf5
("sched/rt: Fix SCHED_RR across cgroups")
e221d028bb08b47e624c5f0a31732c642db9d19a
("sched,rt: fix isolated CPUs leaving root_
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
> Cc: stable@vger.kernel.org
Acked-by: Li Ze
iteration, which actually reduces LOC.
>
> Signed-off-by: Tejun Heo
> Cc: stable@vger.kernel.org
Good catch!
Acked-by: Li Zefan
--
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 http://vger.kernel.org/majordomo-info.html
On 2014/1/28 23:32, Tejun Heo wrote:
> cgroup_create() was returning 0 after allocation failures. Fix it.
>
> Signed-off-by: Tejun Heo
> Cc: stable@vger.kernel.org
Acked-by: Li Zefan
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body
by: Andrew Honig
Signed-off-by: Paolo Bonzini
[ lizf: backported to 3.4: based on Paolo's backport hints for <3.10 ]
Signed-off-by: Li Zefan
---
Paolo's backport hints is here:
http://lkml.org/lkml/2013/12/16/176
---
arch/x86/kvm/lapic.c | 24 ++--
ar
On 2014/1/13 17:38, Jack Wang wrote:
> On 01/13/2014 08:28 AM, Li Zefan wrote:
>> We have several long-term and extended stable kernels, and it's possible
>> that a bug fix is in some stable versions but is missing in some other
>> versions, so I've written a
On 2014/1/13 23:57, Greg Kroah-Hartman wrote:
> On Mon, Jan 13, 2014 at 03:28:11PM +0800, Li Zefan wrote:
>> We have several long-term and extended stable kernels, and it's possible
>> that a bug fix is in some stable versions but is missing in some other
>> versions, s
We have several long-term and extended stable kernels, and it's possible
that a bug fix is in some stable versions but is missing in some other
versions, so I've written a script to find out those fixes.
Take 3.4.xx and 3.2.xx for example. If a bug fix was merged into upstream
kernel after 3.4, an
The patch should be sent to jffs2 mainling list, which is
linux-...@lists.infradead.org.
It's not needed to cc stable mailing list. Actually I think it's
better not to.
On 2013/12/18 10:14, Wang Nan wrote:
> From: Wang Guoli
>
> If jffs2_new_inode() succeeds, it returns with f->sem held, and
>
于 2013/11/18 18:00, Fan Du 写道:
>
>
> On 2013年11月18日 15:00, Li Zefan wrote:
>> On 2013/11/18 14:48, Fan Du wrote:
>>>
>>>
>>> On 2013年11月18日 14:42, Zhao Hongjiang wrote:
>>>> On 2013/11/18 14:36, Fan Du wrote:
>>>>> Hi, HongJi
On 2013/11/18 14:48, Fan Du wrote:
>
>
> On 2013年11月18日 14:42, Zhao Hongjiang wrote:
>> On 2013/11/18 14:36, Fan Du wrote:
>>> Hi, HongJiang
>>>
>>> On 2013年11月18日 14:25, Zhao Hongjiang wrote:
Hi, Fan or Andrew,
74e3d1e17b2e11d175970b85acd44f5927000ba2
include/linux/fs.h: disa
> This bug was introduce in commit 2e8ac30312973dd20e68073653
> (the first time rdev_set_badblock was call from interrupt context),
> so this patch is appropriate for 3.5 and subsequent kernels.
>
While this patch is harmless for 3.4, the changelog does say
it is for 3.5+.
> Signed-off-by: Bian
.39 && <= 3.6. I've
reproduced the bug and tested the fix in 3.4 stable kernel.
--
Li Zefan
--
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 http://vger.kernel.org/majordomo-info.html
On 2013/9/22 9:32, Weng Meiling wrote:
> Hi Li or Tejun,
>
> f169007b2773f285e098cb84c74aac0154d65ff7
> cgroup: fail if monitored file and event_control are in different cgroup
>
> This looks applicable to stable-3.4, that fixed the wrong usage notification,
> even the access to NULL pointer when
c: Jens Axboe
Signed-off-by: James Bottomley
[lizf: backported to 3.4:
- Use __bio_for_each_segment() instead of bio_for_each_segment_all()]
Signed-off-by: Li Zefan
---
fs/bio.c | 20 +++-
1 file changed, 15 insertions(+), 5 deletions(-)
diff --git a/fs/bio.c b/fs/bio.c
index 84
igned-off-by: Roland Dreier
Tested-by: David Milburn
Cc: Jens Axboe
Signed-off-by: James Bottomley
[lizf: backported to 3.0:
- Use __bio_for_each_segment() instead of bio_for_each_segment_all()]
Signed-off-by: Li Zefan
---
fs/bio.c | 20 +++-
1 file changed, 15 insertions(+), 5 dele
_bug.cgi?id=51701
[lizf: Backported to 3.4:
- Adjust context
- Incorporate earlier logging cleanup in process_one_work() from
044c782ce3a9 ('workqueue: fix checkpatch issues')]
Signed-off-by: Li Zefan
---
The original commit was tagged with stable, and it was back
ctly bumping cwq->nr_active.
tj: Updated comment and description.
Signed-off-by: Lai Jiangshan
Signed-off-by: Tejun Heo
[lizf: backported to 3.4: adjust context]
Signed-off-by: Li Zefan
---
The original commit was tagged with stable, and it was backported to 3.2
and 3.6.
Hi David,
On 2013/8/22 16:23, David Miller wrote:
> From: Jesper Dangaard Brouer
> Date: Thu, 22 Aug 2013 10:04:26 +0200
>
>> So, for future reference:
>>
>> Stable patches for the networking tree, I should:
>> 1) check http://patchwork.ozlabs.org/bundle/davem/stable/?state=*
>>to see if my
Hi David,
On 2013/8/22 16:23, David Miller wrote:
> From: Jesper Dangaard Brouer
> Date: Thu, 22 Aug 2013 10:04:26 +0200
>
>> So, for future reference:
>>
>> Stable patches for the networking tree, I should:
>> 1) check http://patchwork.ozlabs.org/bundle/davem/stable/?state=*
>>to see if my
On 2013/8/9 8:00, Greg Kroah-Hartman wrote:
> On Thu, Aug 08, 2013 at 12:08:47PM +0800, Li Zefan wrote:
>> Hi Greg,
>>
>> Could you queue this commit for 3.0 and 3.4? It has been acked by Ingo.
>
> I've already done so, please look at the stable-queue.
>
Oh,
Hi Greg,
Could you queue this commit for 3.0 and 3.4? It has been acked by Ingo.
On 2013/8/2 19:14, Ingo Molnar wrote:
>
> * Li Zefan wrote:
>
>> commit a59f4e079d19464eebb9b06513a1d4f55fdae5ba
>> Author: Zhu Yanhai
>> Date: Tue Jan 8 12:56:52 2013 +0800
>
The bug can crash the kernel, which can be reproduced by the test program
in the changelog.
The fix can be applied to kernels >= 2.6.38 && <= 3.4.
commit 9c5da09d266ca9b32eb16cf940f8161d949c2fe5
Author: Salman Qazi
Date: Thu Jun 14 15:31:09 2012 -0700
perf: Use css_tryget() to avoid propp
On 2013/8/6 15:23, Yijing Wang wrote:
> v1->v2: Update patch log, remove Joe's reported-by, because his problem
> was mainly caused by BIOS incorrect setting. But this patch mainly
> to fix the bug caused by device hot add. Conservatively, this
> version only up
be applicable to kernels >= 3.0 && <= 3.7.
--
Li Zefan
--
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 http://vger.kernel.org/majordomo-info.html
Hi Greg,
> --- a/kernel/cgroup.c
> +++ b/kernel/cgroup.c
> @@ -2769,13 +2769,17 @@ static void cgroup_cfts_commit(struct cg
> {
> LIST_HEAD(pending);
> struct cgroup *cgrp, *n;
> + struct super_block *sb = ss->root->sb;
>
> /* %NULL @cfts indicates abort and don't bother i
commit a59f4e079d19464eebb9b06513a1d4f55fdae5ba
Author: Zhu Yanhai
Date: Tue Jan 8 12:56:52 2013 +0800
sched: Fix the broken sched_rr_get_interval()
Without this patch, syscall sched_rr_get_interval() can return wrong
value, and the bug was introduced in 2.6.24, so this looks like a
candid
Cc: Ben Greear
Cc: Tejun
Hi Willy,
This patch introduced a bug, which was then fixed by commit 34376a50fb1f
("Fix lockup related to stop_machine being stuck in __do_softirq."),
do we need this fix for 2.6.32 ?
On 2013/6/5 1:23, Willy Tarreau wrote:
> 2.6.32-longterm review patch. If anyone has
On 2013/7/29 11:15, zhangwei(Jovi) wrote:
> On 2013/7/29 11:02, Li Zefan wrote:
>> On 2013/7/29 9:33, zhangwei(Jovi) wrote:
>>> commit 11034ae9c20f4057a6127fc965906417978e69b2 upstream
>>>
>>
>> I don't think the stable versions that contain this fix
On 2013/7/29 9:33, zhangwei(Jovi) wrote:
> commit 11034ae9c20f4057a6127fc965906417978e69b2 upstream
>
I don't think the stable versions that contain this fix have been released,
so I think you should ask Greg to drop the patch and resend the patch with
this fix folded.
> Initialization of variab
On 2013/7/23 5:24, KOSAKI Motohiro wrote:
>> I review what I can, but recently have often missed the 2 day review
>> period.
>>
>> Review from the authors and maintainers is probably more valuable than
>> that from generalists on the stable list.
>
>>From point of subsystem developers view, the pr
On 2013/7/23 9:39, Steven Rostedt wrote:
> On Tue, 2013-07-23 at 09:26 +0800, Li Zefan wrote:
>
>> IT companies in China, they try to make sure there's at least one (most the
>> time the result is just one) female developer/tester in a team, and a team
>> is ~10 peopl
On 2013/7/21 21:22, Ric Wheeler wrote:
> On 07/20/2013 01:04 PM, Ben Hutchings wrote:
>> n Fri, 2013-07-19 at 13:42 -0500, Felipe Contreras wrote:
>>> >On Fri, Jul 19, 2013 at 7:08 AM, Ingo Molnar wrote:
> >
> >* Felipe Contreras wrote:
>>> >
> > >>As Linus already pointed out, not
> Perhaps what might help here is a kernel organizational chart. A graph
> of who sends pull requests to Linus, and their subsystem maintainers.
> For example, in the USB "branch" there would be:
>
> Linus Torvalds
> (Linux kernel release engine
igned-off-by: Li Zefan
Signed-off-by: Tejun Heo
[ backported to 3.9:
- fixed build error: added '&' to atomic_inc_not_zero parameter;
this was fixed upstream by commit e8c82d20a9f729cf4b9f73043f7fd4e0872bebfd ]
---
kernel/cgroup.c | 9 -
1 file changed, 8 insertions(+),
igned-off-by: Li Zefan
Signed-off-by: Tejun Heo
[ backported to 3.10:
- fixed build error: added '&' to atomic_inc_not_zero parameter;
this was fixed upstream by commit e8c82d20a9f729cf4b9f73043f7fd4e0872bebfd ]
---
kernel/cgroup.c | 9 -
1 file changed, 8 insert
On 2013/7/18 2:06, Greg KH wrote:
> The patch below seems to reference a patch that showed up in 3.11-rc1,
> so why would it be relevant for the 3.10 or other stable kernels?
>
Tejun must have made a mistake.
I've confirmed <=3.10 kernels are fine, so you can drop it.
> thanks,
>
> greg k-h
>
On 2013/7/17 4:10, Willy Tarreau wrote:
> On Tue, Jul 16, 2013 at 03:43:09PM -0400, Steven Rostedt wrote:
>> On Tue, 2013-07-16 at 12:11 -0700, Greg Kroah-Hartman wrote:
>>
>>> People mark stable patches that way already today with a:
>>> Cc: stable # delay for 3.12-rc4
>>> or some such wordin
On 2013/7/17 8:45, Andrew Morton wrote:
> On Tue, 16 Jul 2013 16:40:09 -0700 Kamal Mostafa wrote:
>
>> On Tue, 2013-07-16 at 16:06 -0700, Andrew Morton wrote:
>>> On Tue, 16 Jul 2013 15:54:02 -0700 Kamal Mostafa
>>> wrote:
>>>
This is a note to let you know that I have just added a patch t
On 2013/7/16 6:08, Steven Rostedt wrote:
> On Mon, 2013-07-15 at 14:50 -0700, Linus Torvalds wrote:
>> On Mon, Jul 15, 2013 at 1:41 PM, Sarah Sharp
>> wrote:
>>>
>>> Oh, FFS, I just called out on private email for "playing the victim
>>> card". I will repeat: this is not just about me, or other m
>> Sarah, first off, I don't have that many tools at hand. Secondly, I
>> simply don't believe in being polite or politically correct.
>
> Bullshit. I've seen you be polite, and explain to clueless maintainers
> why there's no way you can revert their merge that caused regressions,
> and ask them
> It is *my* conception of the stable branch, but I think that many people
> have different expectations about what should be merged or not. For example
> in old LTS branches, I used to merge what was relevant for servers only,
We have lots of embeded systems running 2.6.32 kernel. And we encounte
On 2013/7/12 8:50, Theodore Ts'o wrote:
> On Thu, Jul 11, 2013 at 03:01:17PM -0700, Greg Kroah-Hartman wrote:
>>
>> I'm sitting on top of over 170 more patches that have been marked for
>> the stable releases right now that are not included in this set of
>> releases. The fact that there ar
On 2013/7/3 19:20, Luis Henriques wrote:
> Hi,
>
> While working on backporting commits to the 3.5 kernel, I came across
> this commit which is tagged for stable kernels:
>
> 084457f284abf6789d90509ee11dae383842b23b cgroup: fix umount vs
> cgroup_cfts_commit() race
>
> This commit, however, see
On 2013/6/11 5:13, Greg Kroah-Hartman wrote:
> On Fri, Jun 07, 2013 at 05:00:33PM +0800, Li Zefan wrote:
>> commit 6a76f8c0ab19f215af2a3442870eeb5f0e81998d upstream.
>>
>> Currently set_ftrace_pid and set_graph_function files use seq_lseek
>> for their fops. However se
On 2013/6/7 23:10, Greg KH wrote:
> On Fri, Jun 07, 2013 at 05:09:16PM +0800, Li Zefan wrote:
>> On 2013/5/25 2:23, Greg KH wrote:
>>> I'm announcing the release of the 3.0.80 kernel.
>>>
>>> All users of the 3.0 kernel series must upgrade.
>>&
On 2013/5/31 21:06, Ben Hutchings wrote:
> I'm announcing the release of the 3.2.46 kernel.
>
> All users of the 3.2 kernel series should upgrade.
>
> The updated 3.2.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> linux-3.2.y
> and c
On 2013/5/25 2:23, Greg KH wrote:
> I'm announcing the release of the 3.0.80 kernel.
>
> All users of the 3.0 kernel series must upgrade.
>
> The updated 3.0.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> linux-3.0.y
> and can be brows
[ lizf: adjust context ]
Signed-off-by: Li Zefan
---
kernel/trace/ftrace.c | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
index b17a3f6..0d704b0 100644
--- a/kernel/trace/ftrace.c
+++ b/kernel/trace
eek().
Link:
http://lkml.kernel.org/r/1365663302-2170-1-git-send-email-namhy...@kernel.org
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Namhyung Kim
Signed-off-by: Namhyung Kim
Signed-off-by: Steven Rostedt
[ lizf: adjust context ]
Signed-off-by: Li Zefan
---
include/linux/ftrace.h | 2 +-
ker
[ lizf: adjust context ]
Signed-off-by: Li Zefan
---
include/linux/ftrace.h | 3 ++-
kernel/trace/ftrace.c | 28 ++--
2 files changed, 16 insertions(+), 15 deletions(-)
diff --git a/include/linux/ftrace.h b/include/linux/ftrace.h
index 8add291..f80ca4a 100644
--- a
eek().
Link:
http://lkml.kernel.org/r/1365663302-2170-1-git-send-email-namhy...@kernel.org
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Namhyung Kim
Signed-off-by: Namhyung Kim
Signed-off-by: Steven Rostedt
[ lizf: adjust context ]
Signed-off-by: Li Zefan
---
kernel/trace/ftrace.c | 10 +-
On 2013/6/6 4:05, Greg KH wrote:
> On Tue, Jun 04, 2013 at 03:06:25PM +0800, Li Zefan wrote:
>> Hi Greg,
>>
>> I noticed this patch has been merged into 3.2, 3.5, 3.6 and 3.8, but it was
>> never
>> queued for 3.0 or 3.4. Seems something went wrong, and I actual
Hi Greg,
I noticed this patch has been merged into 3.2, 3.5, 3.6 and 3.8, but it was
never
queued for 3.0 or 3.4. Seems something went wrong, and I actually can trigger
this bug in 3.4 stable kernel.
On 2013/4/15 2:33, gre...@linuxfoundation.org wrote:
>
> This is a note to let you know that I'
On 2013/5/22 16:31, CAI Qian wrote:
> Reproduced on a few systems.
> CAI Qian
>
> created 375 sockets
> Generating file descriptors
> Added 45 filenames from /dev
> Added 19858 filenames from /proc
> Added 11816 filenames from /sys
> [1143] Random reseed: 1433907474
> trinity(1143): Randomne
On 2013/5/10 14:08, Jianguo Wu wrote:
> Hi Greg,
> I rebase "[PATCH] hugetlbfs: fix mmap failure in unaligned size request" on
> 3.4,
> could you please apply to 3.4-stable.
>
Then you should also backport this commit to 3.4:
091d0d55b286c9340201b4ed4470be87fc568228
("shm: fix null pointer dere
On 2013/4/25 6:42, Guenter Roeck wrote:
> On Mon, Apr 08, 2013 at 04:34:26PM -0400, Prarit Bhargava wrote:
>>
>>
>> On 04/08/2013 04:19 PM, John Stultz wrote:
>>> On 04/08/2013 05:47 AM, Prarit Bhargava wrote:
>>
A simple check for an overflow can resolve this problem. Using KTIME_MAX
>>
On 2013/3/27 17:27, zhangwei(Jovi) wrote:
> From: "zhangwei(Jovi)"
>
> Using perf command: perf stat -e ftrace:function ls
>
> this will cause kernel warning and oops.
>
> [ 797.828904] [ cut here ]
> [ 797.828946] WARNING: at include/linux/ftrace.h:209
> ftrace_ops_c
On 2013/3/22 17:31, Ming Lei wrote:
> On Fri, Mar 22, 2013 at 1:48 PM, Li Zefan wrote:
>> On 2013/3/21 12:48, Ming Lei wrote:
>>
>> Yes, it can...As I said, it's irrelevant, because it's vfs that changes
>> file->f_pos.
>>
>> SYSCALL_DEFINE
On 2013/3/21 12:48, Ming Lei wrote:
> On Thu, Mar 21, 2013 at 11:28 AM, Li Zefan wrote:
>> On 2013/3/21 11:17, Ming Lei wrote:
>>> On Thu, Mar 21, 2013 at 10:41 AM, Li Zefan wrote:
>>>>
>>>> In fact the same race exists between readdir() and read()/write
On 2013/3/21 11:17, Ming Lei wrote:
> On Thu, Mar 21, 2013 at 10:41 AM, Li Zefan wrote:
>>
>> In fact the same race exists between readdir() and read()/write()...
>
> Fortunately, no read()/write() are implemented on sysfs directory, :-)
>
That's irrelev
On 2013/3/20 23:25, Ming Lei wrote:
> While readdir() is running, lseek() may set filp->f_pos as zero,
> then may leave filp->private_data pointing to one sysfs_dirent
> object without holding its reference counter, so the sysfs_dirent
> object may be used after free in next readdir().
>
> This pa
On 2013/2/7 18:04, Maxim Uvarov wrote:
> 2013/2/7 Li Zefan :
>> CC: Tejun
>>
>> 于 2013/2/6 23:16, Maxim Uvarov wrote:
>>> linux-3.0.y has put_css_set a litte bit down in the code,
>>> this should not be duplicated.
>>
>> Why do you want to mak
CC: Tejun
于 2013/2/6 23:16, Maxim Uvarov wrote:
> linux-3.0.y has put_css_set a litte bit down in the code,
> this should not be duplicated.
Why do you want to make this change? Have you encountered some kernel bug that
relates
to cgroup?
> Signed-off-by: Maxim Uvarov
NAck
> ---
> kernel/cg
I encountered this build error, and found this patch, but it has been
ignored?
On 2012/11/14 5:50, Vinson Lee wrote:
> This patch fixes this build error with older versions of bison.
>
> CC util/sysfs.o
> BISON util/pmu-bison.c
> util/pmu.y:2.14-24: syntax error, unexpected string, expect
On 2012/11/13 11:01, Tejun Heo wrote:
> cgroup_create_dir() does weird dancing with dentry refcnt. On
> success, it gets and then puts it achieving nothing. On failure, it
> puts but there isn't no matching get anywhere leading to the following
> oops if cgroup_create_file() fails for whatever re
1 - 100 of 102 matches
Mail list logo
