Message-Id: <E1Pm1so-00025V-Am@be1.7eggert.dyndns.org>
From: Bodo Eggert 
	<arcoristkaputtundbrauchtdiesentext.7eggert@nurfuerspam.de>
Subject: Re: [PATCH] NX protection for kernel data : fix 32 bits S3 suspend
To: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
        castet.matthieu@free.fr,
        Linux Kernel list <linux-kernel@vger.kernel.org>,
        linux-security-module@vger.kernel.org, Matthias Hopf <mhopf@suse.de>,
        rjw@sisk.pl, Andrew Morton <akpm@linux-foundation.org>,
        Thomas Gleixner <tglx@linutronix.de>
Reply-To: 7eggert@nurfuerspam.de
Date: Sun, 06 Feb 2011 11:30:17 +0100
References: <ghb2G-3tw-7@gated-at.bofh.it> <ghjtg-WV-5@gated-at.bofh.it> <ghosV-TN-9@gated-at.bofh.it> <ghEo1-2IF-1@gated-at.bofh.it> <gifGW-7eL-13@gated-at.bofh.it>
User-Agent: KNode/0.10.9
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8Bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1009
Lines: 20

H. Peter Anvin <hpa@zytor.com> wrote:

> In static_protections() we have:
> 
>>         /*
>>          * The BIOS area between 640k and 1Mb needs to be executable for
>>          * PCI BIOS based config access (CONFIG_PCI_GOBIOS) support.
>>          */

I don't think the CGA/MDA/VGA graphics memory areas should be executable,
and I doubt execute access to these areas is required - is it?

0xA000:0000 might be a BIOS area, if it is, you don't have a VGA and the
ROM will be exactly 64K. 0xB800 and 0xB000 SHOULD NOT be a ROM, nobody dared
to use it (I don't remember exactly where ROMs are searched).
-- 
Funny quotes:
34. If FedEx and UPS were to merge, would they call it Fed UP?

Friß, Spammer: igc@vhFgi.7eggert.dyndns.org fdnJu@jQOez.7eggert.dyndns.org

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/