linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gyan Gupta <gyan.gupta@intel.com>
To: gyan.gupta@intel.com, x86-ml <x86@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Sean Christopherson <sean.j.christopherson@intel.com>,
	Tony Luck <tony.luck@intel.com>
Subject: [PATCH -v2] x86/msr: Filter MSR writes
Date: Mon, 22 Jun 2020 19:52:28 +0530	[thread overview]
Message-ID: <1592835748-4589-1-git-send-email-gyan.gupta@intel.com> (raw)

From: Borislav Petkov <bp@alien8.de>

> The whitelist is still TBD, I might be able to remove it competely and defer the
> whole whitelisting to the future. when people start reporting MSRs (see
> pr_err_ratelimited() call below).

I am also working on a similar functionality where we allow specific MSRs(whitelisted MSRs) to be allowed to read & write.
Additionally, writes are subjected to checks where only certain bits can be allowed to be modified. This is to increase security & safety of system.
For example, MCi_CTL can be used to enable/disable error reporting of hw unit. So in our use case once error reporting is enabled, it must 
not be disabled. Also we want to have restrictions on rdmsr for security purposes.

- Gyan


             reply	other threads:[~2020-06-22 14:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 14:22 Gyan Gupta [this message]
2020-06-22 15:19 ` [PATCH -v2] x86/msr: Filter MSR writes Borislav Petkov
  -- strict thread matches above, loose matches on Subject: below --
2020-06-12 10:50 [RFC PATCH] " Borislav Petkov
2020-06-13 15:48 ` [PATCH -v2] " Borislav Petkov

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=1592835748-4589-1-git-send-email-gyan.gupta@intel.com \
    --to=gyan.gupta@intel.com \
    --cc=bp@alien8.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).