Re: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally

On Tue, 5 Jun 2007, David Rientjes wrote:

> Reverts git commit c596d9f320aaf30d28c1d793ff3a976dee1db8f5.
> 
> OOM-killed tasks, marked as TIF_MEMDIE, should not be able to access 
> memory outside its cpuset because it could potentially cause other 
> exclusive cpusets to OOM themselves.

Those terminating tasks need that memory to terminate properly right?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally
  - From: David Rientjes <[email protected]>

References:
- [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally
  - From: David Rientjes <[email protected]>

Prev by Date: Re: [PATCH TRIVIAL] icom whitespace cleanups
Next by Date: Re: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally
Previous by thread: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally
Next by thread: Re: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]