From: "H. Peter Anvin" <hpa@zytor.com>
To: 7eggert@nurfuerspam.de
Cc: Bodo Eggert
<arcoristkaputtundbrauchtdiesentext.7eggert@nurfuerspam.de>,
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>
Subject: Re: [PATCH] NX protection for kernel data : fix 32 bits S3 suspend
Date: Sun, 06 Feb 2011 15:32:34 -0800 [thread overview]
Message-ID: <4D4F2F92.9080902@zytor.com> (raw)
In-Reply-To: <E1Pm1so-00025V-Am@be1.7eggert.dyndns.org>
On 02/06/2011 02:30 AM, Bodo Eggert wrote:
> 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).
0xA0000..0xBFFFF can be ROM if you don't have a VGA card; this is new in
PCI 3.x IIRC. However, in legacy systems you will not have ROM in this
area.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2011-02-06 23:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ghb2G-3tw-7@gated-at.bofh.it>
[not found] ` <ghjtg-WV-5@gated-at.bofh.it>
[not found] ` <ghosV-TN-9@gated-at.bofh.it>
[not found] ` <ghEo1-2IF-1@gated-at.bofh.it>
[not found] ` <gifGW-7eL-13@gated-at.bofh.it>
2011-02-06 10:30 ` [PATCH] NX protection for kernel data : fix 32 bits S3 suspend Bodo Eggert
2011-02-06 23:32 ` H. Peter Anvin [this message]
2011-01-31 23:03 matthieu castet
2011-02-01 8:02 ` Ingo Molnar
2011-02-01 13:25 ` castet.matthieu
2011-02-01 16:30 ` H. Peter Anvin
2011-02-02 6:26 ` Ingo Molnar
2011-02-03 22:11 ` H. Peter Anvin
2011-02-05 1:12 ` H. Peter Anvin
2011-02-05 16:46 ` castet.matthieu
2011-02-06 23:41 ` H. Peter Anvin
2011-02-07 7:40 ` Ingo Molnar
2011-02-07 19:59 ` castet.matthieu
2011-02-07 20:04 ` H. Peter Anvin
2011-02-12 16:10 ` matthieu castet
2011-02-14 20:55 ` H. Peter Anvin
2011-02-26 3:58 ` Pavel Machek
2011-02-07 20:07 ` H. Peter Anvin
2011-02-14 21:19 ` H. Peter Anvin
2011-02-14 22:50 ` Rafael J. Wysocki
2011-02-07 3:56 ` H. Peter Anvin
2011-02-07 5:16 ` H. Peter Anvin
2011-02-07 13:16 ` Matthias Hopf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D4F2F92.9080902@zytor.com \
--to=hpa@zytor.com \
--cc=7eggert@nurfuerspam.de \
--cc=akpm@linux-foundation.org \
--cc=arcoristkaputtundbrauchtdiesentext.7eggert@nurfuerspam.de \
--cc=castet.matthieu@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mhopf@suse.de \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox