linux-kernel - Re: [patch] oom: prevent livelock when oom_kill_allocating

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 30 Apr 2009 15:49:20 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	David Rientjes <rientjes@...gle.com>
Cc:	npiggin@...e.de, linux-kernel@...r.kernel.org
Subject: Re: [patch] oom: prevent livelock when oom_kill_allocating_task is
 set

On Thu, 30 Apr 2009 15:38:53 -0700 (PDT)
David Rientjes <rientjes@...gle.com> wrote:

> When /proc/sys/vm/oom_kill_allocating_task is set for large systems that
> want to avoid the lengthy tasklist scan, it's possible to livelock if
> current is ineligible for oom kill.  This normally happens when it is set
> to OOM_DISABLE, but is also possible if any threads are sharing the same
> ->mm with a different tgid.

OK...  And how does the patch address this problem?

<reads the code>

Seems that if we were unable to kill `current', we'll ignore the
oom_kill_allocating_task setting and will fall back the slow tasklist
scan?

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