All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: Dave Hansen <dave@sr71.net>,
	linux-kernel@vger.kernel.org, penguin-kernel@i-love.sakura.ne.jp,
	x86@kernel.org, akpm@linux-foundation.org,
	suresh.b.siddha@intel.com, khlebnikov@openvz.org,
	bhelgaas@google.com
Subject: Re: [PATCH] do not try to sync identity map for non-mapped pages
Date: Sun, 7 Apr 2013 19:25:45 +0200	[thread overview]
Message-ID: <20130407172545.GF31299@pd.tnic> (raw)
In-Reply-To: <51619FFF.30705@linux.intel.com>

On Sun, Apr 07, 2013 at 09:34:07AM -0700, H. Peter Anvin wrote:
> We shouldn't, no. /dev/mem really needs to be fixed along a bunch of
> axes. Yes, it is privileged and extra creepy, but it should either
> work or it should fail cleanly.

Can't we filter out accesses through /dev/mem and not BUG_ON in
__phys_addr() if they come through /dev/mem? Simply fail cleanly. No
idea whether we'll break something still reading /dev/mem though.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-04-07 17:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 16:31 [PATCH] do not try to sync identity map for non-mapped pages Dave Hansen
2013-03-07 21:59 ` [tip:x86/urgent] x86: Do " tip-bot for Dave Hansen
2013-03-07 22:05 ` [PATCH] do " Tetsuo Handa
2013-03-07 22:13   ` H. Peter Anvin
2013-04-07 13:33 ` Borislav Petkov
2013-04-07 16:34   ` H. Peter Anvin
2013-04-07 17:25     ` Borislav Petkov [this message]
2013-04-08 20:33     ` Dave Hansen
  -- strict thread matches above, loose matches on Subject: below --
2013-03-06 23:10 Dave Hansen
2013-03-07 10:19 ` Tetsuo Handa

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=20130407172545.GF31299@pd.tnic \
    --to=bp@alien8.de \
    --cc=akpm@linux-foundation.org \
    --cc=bhelgaas@google.com \
    --cc=dave@sr71.net \
    --cc=hpa@linux.intel.com \
    --cc=khlebnikov@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=suresh.b.siddha@intel.com \
    --cc=x86@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.