From: Andi Kleen <andi@firstfloor.org>
To: "H. Peter Anvin" <h.peter.anvin@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: RFC: Tainting the kernel on raw I/O access
Date: Wed, 03 Sep 2014 16:46:18 -0700 [thread overview]
Message-ID: <87tx4op8s5.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <5407863B.9030608@intel.com> (H. Peter Anvin's message of "Wed, 03 Sep 2014 14:20:59 -0700")
"H. Peter Anvin" <h.peter.anvin@intel.com> writes:
> In a meeting earlier today, we discussed MSR access and that it could be
> used to do bad things. The same applies to other forms of raw I/O
> (/dev/mem, /dev/port, ioperm, iopl, etc.)
I don't think it makes sense to use the taint flags as a security
mechanism. They would be a very poor (and likely by itself insecure) one.
As for the original purpose of taints, I'm not aware of any
problems with MSR access or port IO causing excessive
kernel oops reports. Are you?
If there are none I don't think it makes sense.
At least personally I use MSR accesses quite frequently
for benign purposes.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2014-09-03 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 21:20 RFC: Tainting the kernel on raw I/O access H. Peter Anvin
2014-09-03 22:15 ` Matthew Garrett
2014-09-03 22:20 ` One Thousand Gnomes
2014-09-03 22:25 ` H. Peter Anvin
2014-09-04 15:56 ` One Thousand Gnomes
2014-09-03 23:46 ` Andi Kleen [this message]
2014-09-04 14:10 ` Austin S Hemmelgarn
2014-09-04 16:43 ` One Thousand Gnomes
2014-09-04 5:07 ` Ingo Molnar
2014-09-04 16:47 ` One Thousand Gnomes
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=87tx4op8s5.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=h.peter.anvin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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