[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190326001817.15413-1-rcampbell@nvidia.com>
Date: Mon, 25 Mar 2019 17:18:16 -0700
From: <rcampbell@...dia.com>
To: <linux-kernel@...r.kernel.org>
CC: Ralph Campbell <rcampbell@...dia.com>,
Craig Bergstrom <craigb@...gle.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Fengguang Wu <fengguang.wu@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Hans Verkuil <hans.verkuil@...co.com>,
Mauro Carvalho Chehab <mchehab@...pensource.com>,
Peter Zijlstra <peterz@...radead.org>,
Sander Eikelenboom <linux@...elenboom.it>,
Sean Young <sean@...s.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>
Subject: [PATCH v2 0/1] x86/mm: Fix limit mmap() of /dev/mem to valid physical
From: Ralph Campbell <rcampbell@...dia.com>
I was debugging with v5.1.0-rc1 and while booting I hit a
kernel BUG at arch/x86/mm/physaddr.c:27
which I fixed with the following patch but now I can't seem
to reproduce the exact setup that triggered it.
Still, it seems like a valid problem and maybe my difficulty
in reproducing it explains why others haven't seen it earlier.
Changes from v1 to v2:
* Updated the change log and patch as suggested by Thomas Gleixner.
Ralph Campbell (1):
x86/mm: Fix limit mmap() of /dev/mem to valid physical addresses
arch/x86/mm/mmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.20.1
Powered by blists - more mailing lists