linux-kernel - Re: [PATCH] x86: tighten kernel image page access rights (re-diff against firstfloor tree)

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: <460BDFF9.76E4.0078.0@novell.com>
Date:	Thu, 29 Mar 2007 14:49:13 +0100
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	"Andi Kleen" <ak@...e.de>
Cc:	<linux-kernel@...r.kernel.org>, <patches@...-64.org>
Subject: Re: [PATCH] x86: tighten kernel image page access rights
	(re-diff against firstfloor tree)

>>> Andi Kleen <ak@...e.de> 29.03.07 14:22 >>>
>On Thursday 29 March 2007 14:01, Jan Beulich wrote:
>> On x86-64, kernel memory freed after init can be entirely unmapped instead
>> of just getting 'poisoned' by overwriting with a debug pattern.
>> 
>> On i386 and x86-64 (under CONFIG_DEBUG_RODATA), kernel text and bug table
>> can also be write-protected.
>> 
>> (Not sure what the symbol 'stext' is good for; can it be removed?)
>
>I see you remove it already

I don't think I do - I just move _stext (on x86-64), but leave stext alone.

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