From: Randy Wright <rwright@hp.com>
To: Matthew Garrett <mjg@redhat.com>
Cc: linux-kernel@vger.kernel.org, tmac@hp.com, hpa@zytor.com, rwright@hp.com
Subject: Re: [PATCH] Fix devmem_is_allowed for below 1MB accesses for an efi machine
Date: Thu, 04 Oct 2012 14:07:49 -0600 [thread overview]
Message-ID: <506DEC95.8050806@hp.com> (raw)
In-Reply-To: <jQpxf-3Cv-1@gated-at.bofh.it>
On 10/02/2012 11:20 PM, Matthew Garrett wrote:
> Oh, right, got you. In that case I think we potentially need a
> finer-grained check on EFI platforms - the EFI memory map is kind enough
> to tell us the difference between unusable regions and io regions, and
> we could avoid access to the unusable ones.
I wanted to mention in this context a patch RFC I posted yesterday as a
distinct thread which is visible as https://lkml.org/lkml/2012/10/3/589
with the subject: [PATCH RFC] function probe_roms accessing improper
addresses on UEFI systems.
While the mechanism is different from Tmac's patch (because probe_roms
runs early in boot, prior to resource structure initialization) the
intent of the change is the same: to prevent a machine check resulting
from access to inappropriate physical addresses.
I will monitor both this thread as well as my own recent RFC posting
since the underlying issues are common.
--
Randy Wright <rwright@hp.com> +1-970-898-0998
next parent reply other threads:[~2012-10-04 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jQim6-6MC-7@gated-at.bofh.it>
[not found] ` <jQiFt-6UB-13@gated-at.bofh.it>
[not found] ` <jQoUx-33k-3@gated-at.bofh.it>
[not found] ` <jQp4d-37r-3@gated-at.bofh.it>
[not found] ` <jQpxf-3Cv-1@gated-at.bofh.it>
2012-10-04 20:07 ` Randy Wright [this message]
2012-10-04 21:06 ` [PATCH] Fix devmem_is_allowed for below 1MB accesses for an efi machine H. Peter Anvin
2012-10-02 21:32 T Makphaibulchoke
2012-10-02 21:50 ` H. Peter Anvin
2012-10-03 4:31 ` Matthew Garrett
2012-10-03 4:44 ` H. Peter Anvin
2012-10-03 5:15 ` Matthew Garrett
2012-10-03 5:13 ` Thavatchai Makphaibulchoke
2012-10-03 5:28 ` Matthew Garrett
2012-10-03 5:35 ` H. Peter Anvin
2012-10-03 5:27 ` H. Peter Anvin
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=506DEC95.8050806@hp.com \
--to=rwright@hp.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=tmac@hp.com \
/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