[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 6 Jun 2007 00:39:20 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Paul Jackson <pj@....com>
Cc: David Rientjes <rientjes@...gle.com>, peterz@...radead.org,
ak@...e.de, clameter@...ulhu.engr.sgi.com,
linux-kernel@...r.kernel.org
Subject: Re: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate
globally
On Wed, 6 Jun 2007 00:34:21 -0700 Paul Jackson <pj@....com> wrote:
> > a separate exclusive cpuset mlock'd a gigantic amount of
> > memory and it could not reliably exit because the mlock continued to
> > allocate outside its own cpuset and eventually OOM'd system-critical tasks
> > or depleated all system memory.
>
> Seems like that mlock code is able then to get great globs of memory
> without returning to user space ... perhaps that's where the fix
> should be ... that code should quit chewing up memory if it's
> marked MEMDIE or some such?
yup. A fix for that is in the pipeline: bale from get_user_pages()
if TIF_MEMDIE is set.
-
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