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: <20130201102545.GA3053@amd.pavel.ucw.cz>
Date:	Fri, 1 Feb 2013 11:25:46 +0100
From:	Pavel Machek <pavel@...x.de>
To:	Phil Turmel <philip@...mel.org>, "H. Peter Anvin" <hpa@...or.com>
Cc:	paul.szabo@...ney.edu.au, ben@...adent.org.uk,
	dave@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, "H. Peter Anvin" <hpa@...or.com>
Subject: PAE problems was [RFC] Reproducible OOM with just a few sleeps


On Fri 2013-02-01 11:20:44, Pavel Machek wrote:
> On Thu 2013-01-31 23:38:27, Phil Turmel wrote:
> > On 01/31/2013 10:13 PM, paul.szabo@...ney.edu.au wrote:
> > > [trim /] Does not that prove that PAE is broken?
> > 
> > Please, Paul, take *yes* for an answer.  It is broken.  You've received
> > multiple dissertations on why it is going to stay that way.  Unless you
> > fix it yourself, and everyone seems to be politely wishing you the best
> > of luck with that.
> 
> It is not Paul's job to fix PAE. It is job of whoever broke it to do
> so.
> 
> If it is broken with 2GB of RAM, it is clearly not the known "lowmem
> starvation" issue, it is something else... and probably worth
> debugging.
> 
> So, Paul, if you have time and interest... Try to find some old kernel
> version where sleep test works with PAE. Hopefully there is one. Then
> do bisection... author of the patch should then fix it. (And if not,
> at least you have patch you can revert.)
> 
> rjw is worth cc-ing at that point.

Ouch, and... IIRC (hpa should know for sure), PAE is neccessary for
R^X support on x86, thus getting more common, not less. If it does not
work, that's bad news.

Actually, if PAE is known broken, it should probably get marked as
such in Kconfig. That's sure to get some discussion started...
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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