Re: [PATCH] fix OOM killing processes wrongly thought MPOL_BIND

On Wed, Apr 18, 2007 at 08:35:22PM +0100, Hugh Dickins wrote:
> I only have CONFIG_NUMA=y for build testing: surprised when trying a memhog
> to see lots of other processes killed with "No available memory (MPOL_BIND)".
> memhog is killed correctly once we initialize nodemask in constrained_alloc().
> Signed-off-by: Hugh Dickins <[email protected]>
> ---
> Perhaps appropriate for 2.6.20-stable too - regression since 2.6.19.

This is a clear fix for an uninitialized variable.


Acked-by: William Irwin <[email protected]>


-- wli
-
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/

---

• References:
  • [PATCH] fix OOM killing processes wrongly thought MPOL_BIND
    • From: Hugh Dickins <[email protected]>

• Prev by Date: Re: Loud "pop" coming from hard drive on reboot
• Next by Date: Re: [PATCH][RFC] Kill off legacy power management stuff.
• Previous by thread: Re: [PATCH] fix OOM killing processes wrongly thought MPOL_BIND
• Next by thread: Re: [PATCH] fix OOM killing processes wrongly thought MPOL_BIND
• 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]