From: Chris Down <chris@chrisdown.name>
To: linux-kernel@vger.kernel.org
Cc: Borislav Petkov <bp@suse.de>, Jakub Kicinski <kuba@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
kernel-team@fb.com, sean.j.christopherson@intel.com,
tony.luck@intel.com, torvalds@linux-foundation.org,
x86@kernel.org
Subject: [PATCH v2 0/2] a couple of userspace MSR filtering improvements
Date: Fri, 21 Aug 2020 13:10:03 +0100 [thread overview]
Message-ID: <cover.1598011595.git.chris@chrisdown.name> (raw)
As discussed in Message-ID <20200714165621.GA3622@nazgul.tnic>.
We all agree that userspace MSR twiddling is non-ideal, but we should be
a bit cautious of taking up too much kmsg buffer if applications do
repeated writes. `allow_writes=1` is possible, but is non-ideal (see
patch 1 changelog).
Also added pid information to the message, since it makes identification
of the source (more or less) unambiguous.
Changes in v2:
- Fixed mostly aesthetic suggestions from Boris. Thanks! :-)
Chris Down (2):
x86: Prevent userspace MSR access from dominating the console
x86: Make source of unrecognised MSR writes unambiguous
arch/x86/kernel/msr.c | 19 ++++++++++++++++---
1 file changed, 16 insertions(+), 3 deletions(-)
--
2.28.0
next reply other threads:[~2020-08-21 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 12:10 Chris Down [this message]
2020-08-21 12:10 ` [PATCH v2 1/2] x86: Prevent userspace MSR access from dominating the console Chris Down
2020-08-21 12:10 ` [PATCH v2 2/2] x86: Make source of unrecognised MSR writes unambiguous Chris Down
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=cover.1598011595.git.chris@chrisdown.name \
--to=chris@chrisdown.name \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=kernel-team@fb.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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.