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: <20100907114223.C907.A69D9226@jp.fujitsu.com>
Date:	Wed,  8 Sep 2010 11:44:07 +0900 (JST)
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	David Rientjes <rientjes@...gle.com>
Cc:	kosaki.motohiro@...fujitsu.com,
	LKML <linux-kernel@...r.kernel.org>,
	linux-mm <linux-mm@...ck.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [BUGFIX for 2.6.36][RESEND][PATCH 1/2] oom: remove totalpage normalization from oom_badness()

> On Tue, 31 Aug 2010, KOSAKI Motohiro wrote:
> 
> > ok, this one got no objection except original patch author.
> 
> Would you care to respond to my objections?
> 
> I replied to these two patches earlier with my nack, here they are:
> 
> 	http://marc.info/?l=linux-mm&m=128273555323993
> 	http://marc.info/?l=linux-mm&m=128337879310476
> 
> Please carry on a useful debate of the issues rather than continually 
> resending patches and labeling them as bugfixes, which they aren't.

You are still talking about only your usecase. Why do we care you? Why?
Why don't you fix the code by yourself? Why? Why do you continue selfish
development? Why? I can't understand.



> > then, I'll push it to mainline. I'm glad that I who stabilization
> > developer have finished this work.
> > 
> 
> You're not the maintainer of this code, patches go through Andrew.
> 
> That said, I'm really tired of you trying to make this personal with me; 
> I've been very respectful and accomodating during this discussion and I 
> hope that you will be the same.

As I said, You only need to don't break userland and fix the code immediately.
You don't have to expect stabilization developer allow userland and code
breakage.



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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ