[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090511141138.3e8118ab.akpm@linux-foundation.org>
Date: Mon, 11 May 2009 14:11:38 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Rientjes <rientjes@...gle.com>
Cc: gregkh@...e.de, npiggin@...e.de, mel@....ul.ie,
a.p.ziljstra@...llo.nl, cl@...ux-foundation.org,
dave@...ux.vnet.ibm.com, san@...roid.com, arve@...roid.com,
linux-kernel@...r.kernel.org
Subject: Re: [patch 05/11 -mmotm] oom: fix possible oom_dump_tasks NULL
pointer
On Sun, 10 May 2009 15:07:16 -0700 (PDT)
David Rientjes <rientjes@...gle.com> wrote:
> When /proc/sys/vm/oom_dump_tasks is enabled, it is possible to get a NULL
> pointer for tasks that have detached mm's since task_lock() is not held
> during the tasklist scan.
ok. But a better changelog would have told us how the patch fixes the
problem?
This patch series is partially core MM and partially drivers/staging.
I don't normally handle staging things, so I'd need to be cherrypicking
from this lot. Is there any interdependency between the two things?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists