Re: [PATCH 1/2 (repost)] mm: serialize OOM kill operations

Dave Peterson <[email protected]> wrote:
>
> Yes I am familiar with this sort of problem.  :-)

Andrea has long advocated that the memory allocator shouldn't infinitely
loop for small __GFP_WAIT allocations.  ie: ultimately we should return
NULL back to the caller.

Usually this will cause the correct process to exit.  Sometimes it won't.

Did you try it?
-
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 1/2 (repost)] mm: serialize OOM kill operations
    • From: Dave Peterson <[email protected]>

• References:
  • [PATCH 1/2 (repost)] mm: serialize OOM kill operations
    • From: Dave Peterson <[email protected]>
  • Re: [PATCH 1/2 (repost)] mm: serialize OOM kill operations
    • From: Andrew Morton <[email protected]>
  • Re: [PATCH 1/2 (repost)] mm: serialize OOM kill operations
    • From: Dave Peterson <[email protected]>

• Prev by Date: Re: [PATCH 1/2 (repost)] mm: serialize OOM kill operations
• Next by Date: [PATCH] symbol_put_addr() locks kernel
• Previous by thread: Re: [PATCH 1/2 (repost)] mm: serialize OOM kill operations
• Next by thread: Re: [PATCH 1/2 (repost)] mm: serialize OOM kill operations
• 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]