From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932470AbdJZTCk (ORCPT ); Thu, 26 Oct 2017 15:02:40 -0400 Received: from mail-wm0-f48.google.com ([74.125.82.48]:46621 "EHLO mail-wm0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932327AbdJZTCd (ORCPT ); Thu, 26 Oct 2017 15:02:33 -0400 X-Google-Smtp-Source: ABhQp+R7eAgxhrAgVwOZcaz2cgyb4ilrMxbI4GpSs2jvUIFRsY5FiL6QXQJ4E9YEbi3PqlTTR94sow== Date: Thu, 26 Oct 2017 21:02:29 +0200 From: Ingo Molnar To: Craig Bergstrom Cc: Sander Eikelenboom , Boris Ostrovsky , Fengguang Wu , wfg@linux.intel.com, linux-kernel@vger.kernel.org, LKP , Linus Torvalds Subject: Re: ce56a86e2a ("x86/mm: Limit mmap() of /dev/mem to valid physical addresses"): kernel BUG at arch/x86/mm/physaddr.c:79! Message-ID: <20171026190229.zt743ooxvjsukmis@gmail.com> References: <20171024024439.u3ywfgvi67fe4mbg@wfg-t540p.sh.intel.com> <440615a7-6cc0-a607-ce7c-22a34b69e8fe@eikelenboom.it> <1d203c07-0595-a33a-620b-c51eea9721d1@eikelenboom.it> <8721eeac-a644-e815-55e9-5f01956dd22a@eikelenboom.it> <20171026163911.dnovh4zaik5qumtt@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Craig Bergstrom 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