lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 26 Oct 2017 21:02:29 +0200
From:   Ingo Molnar <>
To:     Craig Bergstrom <>
Cc:     Sander Eikelenboom <>,
        Boris Ostrovsky <>,
        Fengguang Wu <>,,, 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!

* 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.



Powered by blists - more mailing lists