Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <20171026163911.dnovh4zaik5qumtt@gmail.com>
References: <20171024024439.u3ywfgvi67fe4mbg@wfg-t540p.sh.intel.com>
 <c5082661-99a4-1b11-c8a1-8b31e9ab8d95@oracle.com> <CAOJUGyfTM2J-P29yPhUx2A2SDjA0rv972SE0hmbMHonthMd_bQ@mail.gmail.com>
 <440615a7-6cc0-a607-ce7c-22a34b69e8fe@eikelenboom.it> <1d203c07-0595-a33a-620b-c51eea9721d1@eikelenboom.it>
 <8721eeac-a644-e815-55e9-5f01956dd22a@eikelenboom.it> <CAOJUGye8nXL-J9oArLLMFz-RPRdKFe6EgqtYPSr5kcWoH2EodQ@mail.gmail.com>
 <20171026163911.dnovh4zaik5qumtt@gmail.com>
From:   Craig Bergstrom <craigb@google.com>
Date:   Thu, 26 Oct 2017 11:49:50 -0600
Message-ID: <CAOJUGycO494NcvJk89MMub9Tbrj6FUoSNN4SOci7NgJRKq7v=A@mail.gmail.com>
Subject: Re: ce56a86e2a ("x86/mm: Limit mmap() of /dev/mem to valid physical
 addresses"): kernel BUG at arch/x86/mm/physaddr.c:79!
To:     Ingo Molnar <mingo@kernel.org>
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>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.


On Thu, Oct 26, 2017 at 10:39 AM, Ingo Molnar <mingo@kernel.org> wrote:
>
> * Craig Bergstrom <craigb@google.com> wrote:
>
>> Yes, not much time left for 4.14, it might be reasonable to pull the
>> change out since it's causing problems. [...]
>
> Ok, I'll queue up a revert tomorrow morning and send it to Linus ASAP if there's
> no good fix by then. In hindsight I should have queued it for v4.15 ...
>
> Thanks,
>
>         Ingo

From 1582339026935016708@xxx Thu Oct 26 16:41:29 +0000 2017
X-GM-THRID: 1582105239086831553
X-Gmail-Labels: Inbox,Category Forums