From: <rcampbell@nvidia.com>
To: <linux-kernel@vger.kernel.org>
Cc: Ralph Campbell <rcampbell@nvidia.com>,
Craig Bergstrom <craigb@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Fengguang Wu <fengguang.wu@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hans Verkuil <hans.verkuil@cisco.com>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Peter Zijlstra <peterz@infradead.org>,
Sander Eikelenboom <linux@eikelenboom.it>,
Sean Young <sean@mess.org>, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>
Subject: [PATCH 0/1] x86/mm: Fix limit mmap() of /dev/mem to valid physical
Date: Mon, 18 Mar 2019 15:46:52 -0700 [thread overview]
Message-ID: <20190318224653.26549-1-rcampbell@nvidia.com> (raw)
From: Ralph Campbell <rcampbell@nvidia.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.
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
next reply other threads:[~2019-03-18 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 22:46 rcampbell [this message]
2019-03-18 22:46 ` [PATCH 1/1] x86/mm: Fix limit mmap() of /dev/mem to valid physical addresses rcampbell
2019-03-23 19:02 ` Thomas Gleixner
2019-03-25 22:03 ` Ralph Campbell
2019-03-25 22:55 ` Thomas Gleixner
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=20190318224653.26549-1-rcampbell@nvidia.com \
--to=rcampbell@nvidia.com \
--cc=boris.ostrovsky@oracle.com \
--cc=craigb@google.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=mchehab@s-opensource.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sean@mess.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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