linux-kernel - Re: [PATCH 3/2] oom: clear TIF_MEMDIE after oom_reaper managed to unmap the address space

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 28 Jan 2016 22:51:22 +0100
From:	Michal Hocko <mhocko@...nel.org>
To:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc:	akpm@...ux-foundation.org, hannes@...xchg.org, mgorman@...e.de,
	rientjes@...gle.com, torvalds@...ux-foundation.org,
	oleg@...hat.com, hughd@...gle.com, andrea@...nel.org,
	riel@...hat.com, linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/2] oom: clear TIF_MEMDIE after oom_reaper managed to
 unmap the address space

On Thu 28-01-16 20:24:36, Tetsuo Handa wrote:
[...]
> I like the OOM reaper approach but I can't agree on merging the OOM reaper
> without providing a guaranteed last resort at the same time. If you do want
> to start the OOM reaper as simple as possible (without being bothered by
> a lot of possible corner cases), please pursue a guaranteed last resort
> at the same time.

I am getting tired of this level of argumentation. oom_reaper in its
current form is a step forward. I have acknowledged there are possible
improvements doable on top but I do not see them necessary for the core
part being merged. I am not trying to rush this in because I am very
well aware of how subtle and complex all the interactions might be.
So please stop your "we must have it all at once" attitude. This is
nothing we have to rush in. We are not talking about a regression which
has to be absolutely fixed in few days.

-- 
Michal Hocko
SUSE Labs