linux-kernel - Re: 2.6.23.8: OOM killer kills wrong jobs

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] [day] [month] [year] [list]

Message-ID: <Pine.OSF.4.44.0712171046390.285022-100000@alcor.concordia.ca>
Date:	Mon, 17 Dec 2007 10:51:02 -0500 (EST)
From:	Sylvain Robitaille <syl@...or.concordia.ca>
To:	Tao Wang <taow@...or.concordia.ca>
cc:	Steven Winikoff <smw@...or.concordia.ca>,
	<linux-kernel@...r.kernel.org>,
	Sheila Ettinger <sheilae@...or.concordia.ca>,
	Tan Bui <tan@...or.concordia.ca>,
	Gillian Roper <groper@...or.concordia.ca>
Subject: Re: 2.6.23.8: OOM killer kills wrong jobs


(removing Alan Cox from the Cc: list;  He does not need to be involved
in the details of our discussions of local systems ...)

On Mon, 17 Dec 2007 taow@...or.concordia.ca wrote:

> ... Thesis 1,2,3 has 16GB memory. Aries has 12G.

Note that the Theses and Aries are Xeon systems, which are 32-bit systems
in the first place, so the problem described is likely not applicable
to these.  I fully expect that the problem being encountered on Baby Alcor
(and Bonnie?) is specifically because of the large memory configuration,
on a 64-bit system, but running a 32-bit OS configuration.  At least
that's how I understood the explanation.

-- 
----------------------------------------------------------------------
Sylvain Robitaille                              syl@...or.concordia.ca

Systems and Network analyst                       Concordia University
Instructional & Information Technology        Montreal, Quebec, Canada
----------------------------------------------------------------------

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