From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/mtrr changes for v5.6
Date: Tue, 28 Jan 2020 19:29:11 +0100 [thread overview]
Message-ID: <20200128182911.GA109695@gmail.com> (raw)
Linus,
Please pull the latest x86-mtrr-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-mtrr-for-linus
# HEAD: 4fc265a9c9b258ddd7eafbd0dbfca66687c3d8aa x86/mtrr: Require CAP_SYS_ADMIN for all access
Two changes: restrict /proc/mtrr to CAP_SYS_ADMIN, plus a cleanup.
Thanks,
Ingo
------------------>
Borislav Petkov (1):
x86/mtrr: Get rid of mtrr_seq_show() forward declaration
Kees Cook (1):
x86/mtrr: Require CAP_SYS_ADMIN for all access
arch/x86/kernel/cpu/mtrr/if.c | 63 +++++++++++++++----------------------------
1 file changed, 22 insertions(+), 41 deletions(-)
next reply other threads:[~2020-01-28 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 18:29 Ingo Molnar [this message]
2020-01-28 21:15 ` [GIT PULL] x86/mtrr changes for v5.6 pr-tracker-bot
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=20200128182911.GA109695@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.