linux-kernel - Re: NonExecutable Bit in 32Bit

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <462EFB66.1090907@zytor.com>
Date:	Tue, 24 Apr 2007 23:55:34 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"Cestonaro, Thilo \(external\)" 
	<Thilo.Cestonaro.external@...itsu-siemens.com>
CC:	Tuncer Ayaz <tuncer.ayaz@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: NonExecutable Bit in 32Bit

Cestonaro, Thilo (external) wrote:
> Hey,
> 
>> CONFIG_HIGHMEM64G=y
>> CONFIG_HIGHMEM=y
>> CONFIG_X86_PAE=y
> 
> Ok in highmem it's active, whats about lowmem?

It's not highmem vs lowmem, it is that HIGHMEM64G is required for
X86_PAE, which is required for NX support.

> x86-64 is NX active for lowmem too AFAIK.

Good thing, since x86-64 doesn't have highmem (nor does it need it,
since it has enough virtual address space to map all physical address
space and still have left over, like it *should* be.)

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