linux-kernel - Re: Eliminating kernel mixed page (code + data)

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]

Date:	Mon, 14 Sep 2009 08:34:37 -0400
From:	Siarhei Liakh <sliakh.lkml@...il.com>
To:	Eric Lacombe <goretux@...il.com>
Cc:	Mel Gorman <mel@....ul.ie>, Greg KH <gregkh@...e.de>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Eric Lacombe <eric.lacombe@...urity-labs.org>
Subject: Re: Eliminating kernel mixed page (code + data)

> First, is there a kernel option to enforce kernel code and kernel data
> separation among pages ?

I do not think so.

> Otherwise, is it sufficient to enforce page alignment for the start address of
> all data segment, to achieve this goal ?
> (on top of using CONFIG_RELOCATABLE)

AFAIK, this would be required but not sufficient. I am currently
working on a set of patches that:
1. eliminate mixed pages in kernel space
2. keep data as non-executable and code as read-only

As a starting point, you can search for my name in the mailing list to
see the patches and the discussion around them.
--
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/