linux-kernel - Re: [resend][PATCH 2/4] Revert "oom: deprecate oom

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]

Message-Id: <20101101030353.607A.A69D9226@jp.fujitsu.com>
Date:	Mon, 1 Nov 2010 16:06:27 +0900 (JST)
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	David Rientjes <rientjes@...gle.com>
Cc:	kosaki.motohiro@...fujitsu.com,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-mm <linux-mm@...ck.org>
Subject: Re: [resend][PATCH 2/4] Revert "oom: deprecate oom_adj tunable"

> On Tue, 26 Oct 2010, KOSAKI Motohiro wrote:
> 
> > > NACK as a logical follow-up to my NACK for "oom: remove totalpage 
> > > normalization from oom_badness()"
> > 
> > Huh?
> > 
> > I requested you show us justification. BUT YOU DIDNT. If you have any 
> > usecase, show us RIGHT NOW. 
> > 
> 
> The new tunable added in 2.6.36, /proc/pid/oom_score_adj, is necessary for 
> the units that the badness score now uses.  We need a tunable with a much 

Who we?

> higher resolution than the oom_adj scale from -16 to +15, and one that 
> scales linearly as opposed to exponentially.  Since that tunable is much 
> more powerful than the oom_adj implementation, which never made any real 

The reason that you ware NAKed was not to introduce new powerful feature.
It was caused to break old and used feature from applications.


> sense for defining oom killing priority for any purpose other than 
> polarization, the old tunable is deprecated for two years.

You haven't tested your patch at all. Distro's initram script are using
oom_adj interface and latest kernel show pointless warnings 
"/proc/xx/oom_adj is deprecated, please use /proc/xx/oom_score_adj instead."
at _every_ boot time.

As I said, DON'T SEND UNTESTED PATCH! DON'T BREAK USERLAND CARELESSLY!


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