linux-kernel - Re: Regression in 2.6.25-rc3: s2ram segfaults before suspending

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: <47CDD715.3010905@zytor.com>
Date:	Tue, 04 Mar 2008 15:11:17 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	Ingo Molnar <mingo@...e.hu>,
	"Klaus S. Madsen" <ksm@...rnemadsen.org>,
	Pavel Machek <pavel@....cz>,
	Suspend-devel list <suspend-devel@...ts.sourceforge.net>,
	LKML <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: Regression in 2.6.25-rc3: s2ram segfaults before suspending

Jeremy Fitzhardinge wrote:
>>
>> PAE activates NX on 32-bit. So we probably had an NX regression that 
>> got fixed by the side-effects of one of the unifications. Does it 
>> start working if you disable NX via the noexec=off boot option?
> 
> What's the state of play here?  Is upshot that this change fixed a bug 
> which broke s2ram, or caused a bug which broke s2ram?
> 

As far as I can tell, this change fixed a bug, and the fact that the bug 
was fixed triggered a s2ram bug.

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