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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <F7F9B0BE3E9BD449B110D0B1CEF6CAEF05302A20@ABGEX01E.abg.fsc.net>
Date:	Wed, 25 Apr 2007 12:28:51 +0200
From:	"Cestonaro, Thilo \(external\)" 
	<Thilo.Cestonaro.external@...itsu-siemens.com>
To:	"Marat Buharov" <marat.buharov@...il.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: RE: NonExecutable Bit in 32Bit

> > And this prevents the lowmemory to be secured by NX?
> What do you mean, when you say "lowmemory"?

I mean EF-Segments. Cause we got a kernel oops as we accidentally used ioremap_nocache on a EF-Segment address.
Before that usage the EF-Segments weren't secured, afterwards they were.
We use now ioremap which does the high low mem check, but I was a bit confused that NX was not active before.
But I can't provide any further informations about the system, cause it was more or less support for a customer.

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