mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Craig Bergstrom <craigb@google.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Fengguang Wu <fengguang.wu@intel.com>,
	wfg@linux.intel.com, linux-kernel@vger.kernel.org,
	LKP <lkp@01.org>, Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: ce56a86e2a ("x86/mm: Limit mmap() of /dev/mem to valid physical addresses"): kernel BUG at arch/x86/mm/physaddr.c:79!
Date: Thu, 26 Oct 2017 21:02:29 +0200	[thread overview]
Message-ID: <20171026190229.zt743ooxvjsukmis@gmail.com> (raw)
In-Reply-To: <CAOJUGycO494NcvJk89MMub9Tbrj6FUoSNN4SOci7NgJRKq7v=A@mail.gmail.com>


* Craig Bergstrom <craigb@google.com> wrote:

> Sander, thanks for the details, they've been very useful.
> 
> I suspect that your host system's mem=2048M parameter is causing the
> problem.  Any chance you can confirm by removing the parameter and
> running the guest code path?
> 
> More specifically, since you're telling the kernel that it's high
> memory address is at 2048M and your device is at 0xfe1fe000 (~4G), the
> new mmap() limits are preventing you from mapping addresses that are
> explicitly disallowed by the parameter.

Well, 'mem=2048M' shouldn't really limit device memory, it's supposed to limit 
(trim) 'RAM' and not much else.

Thanks,

	Ingo

  reply	other threads:[~2017-10-26 19:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24  2:44 Fengguang Wu
2017-10-25 20:50 ` Boris Ostrovsky
     [not found]   ` <CAOJUGyfTM2J-P29yPhUx2A2SDjA0rv972SE0hmbMHonthMd_bQ@mail.gmail.com>
2017-10-26  8:05     ` Sander Eikelenboom
2017-10-26  8:12       ` Sander Eikelenboom
2017-10-26  8:58         ` Sander Eikelenboom
2017-10-26 16:35           ` Craig Bergstrom
2017-10-26 16:39             ` Ingo Molnar
2017-10-26 17:49               ` Craig Bergstrom
2017-10-26 19:02                 ` Ingo Molnar [this message]
2017-10-26 19:29                   ` Linus Torvalds
2017-10-26 19:50                     ` Craig Bergstrom
2017-10-26 21:12                       ` Linus Torvalds
2017-11-16 15:49                         ` [tip:x86/urgent] x86/mm: Limit mmap() of /dev/mem to valid physical addresses tip-bot for Craig Bergstrom
2017-10-27 19:24                       ` ce56a86e2a ("x86/mm: Limit mmap() of /dev/mem to valid physical addresses"): kernel BUG at arch/x86/mm/physaddr.c:79! Ingo Molnar
2017-10-27 19:28                         ` Craig Bergstrom
2017-11-03 19:54                           ` Craig Bergstrom
2017-10-27  8:25                     ` Ingo Molnar
2017-10-26 19:29                 ` Sander Eikelenboom
2017-10-26 20:01                   ` [Xen-devel] " Andrew Cooper
2017-10-27  7:07                   ` Jan Beulich

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=20171026190229.zt743ooxvjsukmis@gmail.com \
    --to=mingo@kernel.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=craigb@google.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@eikelenboom.it \
    --cc=lkp@01.org \
    --cc=torvalds@linux-foundation.org \
    --cc=wfg@linux.intel.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
all inboxes | Powered by JetHome®