All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: T Makphaibulchoke <tmac@hp.com>
Cc: tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
	akpm@linux-foundation.org, yinghai@kernel.org, tiwai@suse.de,
	viro@zeniv.linux.org.uk, aarcange@redhat.com,
	tony.luck@intel.com, mgorman@suse.de, weiyang@linux.vnet.ibm.com,
	octavian.purdila@intel.com, paul.gortmaker@windriver.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] Fix devmem_is_allowed for below 1MB accesses for an efi machine
Date: Tue, 02 Oct 2012 14:50:09 -0700	[thread overview]
Message-ID: <506B6191.6080605@zytor.com> (raw)
In-Reply-To: <1349213536-3436-1-git-send-email-tmac@hp.com>

On 10/02/2012 02:32 PM, T Makphaibulchoke wrote:
> Changing devmem_is_allowed so that on an EFI machine, access to physical
> address below 1 MB is allowed only to physical pages that are valid in
> the EFI memory map.  This prevents the possibility of an MCE due to
> accessing an invalid physical address.

What?

That sounds like exactly the opposite of normal /dev/mem behavior... we
allow access to non-memory resources (which really could do anything if
misused), but not memory.

You seem like you're flipping it on its head.

	-hpa

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: T Makphaibulchoke <tmac@hp.com>
Cc: tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
	akpm@linux-foundation.org, yinghai@kernel.org, tiwai@suse.de,
	viro@zeniv.linux.org.uk, aarcange@redhat.com,
	tony.luck@intel.com, mgorman@suse.de, weiyang@linux.vnet.ibm.com,
	octavian.purdila@intel.com, paul.gortmaker@windriver.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] Fix devmem_is_allowed for below 1MB accesses for an efi machine
Date: Tue, 02 Oct 2012 14:50:09 -0700	[thread overview]
Message-ID: <506B6191.6080605@zytor.com> (raw)
In-Reply-To: <1349213536-3436-1-git-send-email-tmac@hp.com>

On 10/02/2012 02:32 PM, T Makphaibulchoke wrote:
> Changing devmem_is_allowed so that on an EFI machine, access to physical
> address below 1 MB is allowed only to physical pages that are valid in
> the EFI memory map.  This prevents the possibility of an MCE due to
> accessing an invalid physical address.

What?

That sounds like exactly the opposite of normal /dev/mem behavior... we
allow access to non-memory resources (which really could do anything if
misused), but not memory.

You seem like you're flipping it on its head.

	-hpa


  reply	other threads:[~2012-10-02 21:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 21:32 [PATCH] Fix devmem_is_allowed for below 1MB accesses for an efi machine T Makphaibulchoke
2012-10-02 21:32 ` T Makphaibulchoke
2012-10-02 21:50 ` H. Peter Anvin [this message]
2012-10-02 21:50   ` H. Peter Anvin
2012-10-03  4:31   ` Matthew Garrett
2012-10-03  4:31     ` Matthew Garrett
2012-10-03  4:44     ` H. Peter Anvin
2012-10-03  4:44       ` H. Peter Anvin
2012-10-03  5:15       ` Matthew Garrett
2012-10-03  5:15         ` Matthew Garrett
2012-10-03  5:13         ` Thavatchai Makphaibulchoke
2012-10-03  5:13           ` Thavatchai Makphaibulchoke
2012-10-03  5:28           ` Matthew Garrett
2012-10-03  5:28             ` Matthew Garrett
2012-10-03  5:35             ` H. Peter Anvin
2012-10-03  5:35               ` H. Peter Anvin
2012-10-03  5:27         ` H. Peter Anvin
2012-10-03  5:27           ` H. Peter Anvin
     [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
2012-10-04 21:06           ` 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=506B6191.6080605@zytor.com \
    --to=hpa@zytor.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=octavian.purdila@intel.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=tglx@linutronix.de \
    --cc=tiwai@suse.de \
    --cc=tmac@hp.com \
    --cc=tony.luck@intel.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=weiyang@linux.vnet.ibm.com \
    --cc=x86@kernel.org \
    --cc=yinghai@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.