From: rminnich@gmail.com (ron minnich)
Subject: [TUHS] OT: critical Intel design flaw
Date: Wed, 03 Jan 2018 17:46:03 +0000 [thread overview]
Message-ID: <CAP6exYJUvNuXi1o=wOX+cdkgLx-oDmttJTunzy5zsaMhLxd42g@mail.gmail.com> (raw)
In-Reply-To: <C30F8795-EBB0-4734-8550-0BE2B77F07F0@bitblocks.com>
The type of kernel is orthogonal to this particular design flaw from what I
know. It's about how page tables are set up for user mode processes. I may
be wrong but pretty much every Unix or Unix-like kernel (including Plan 9)
follows the page table model Windows and Linux use: the ring 0 PTEs are
present in the page table, even in user mode, and we count on the
architecture to prevent ring 3 access to ring 0 memory. This is certainly
the case on all the ones I've worked on.
I don't think a microkernel would save you.
This is not a much ado about nothing case: it's early days and people can
make it work: https://twitter.com/brainsmoke/status/948561799875502080
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180103/8dc6e01a/attachment.html>
next prev parent reply other threads:[~2018-01-03 17:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 13:43 Noel Chiappa
2018-01-03 14:26 ` Clem Cole
2018-01-03 17:28 ` Bakul Shah
2018-01-03 17:46 ` ron minnich [this message]
2018-01-03 18:28 ` Bakul Shah
2018-01-03 18:27 ` Clem Cole
2018-01-03 18:39 ` Forrest, Jon
2018-01-03 18:50 ` ron minnich
2018-01-03 19:56 ` Paul Winalski
2018-01-03 20:24 ` Bakul Shah
2018-01-03 23:40 ` Theodore Ts'o
2018-01-04 0:51 ` Larry McVoy
2018-01-04 2:13 ` Bakul Shah
2018-01-04 2:26 ` Larry McVoy
2018-01-04 3:31 ` Bakul Shah
2018-01-04 2:09 ` Arthur Krewat
2018-01-04 3:21 ` Dan Cross
2018-01-04 17:42 ` Arthur Krewat
2018-01-04 11:53 ` Harald Arnesen
2018-01-04 14:03 ` Clem Cole
2018-01-04 15:54 ` Larry McVoy
2018-01-04 16:45 ` Theodore Ts'o
2018-01-04 17:10 ` Andy Kosela
2018-01-04 17:17 ` Larry McVoy
2018-01-04 18:29 ` Bakul Shah
2018-01-04 18:50 ` Larry McVoy
2018-01-04 20:52 ` Warner Losh
2018-01-04 20:56 ` Bakul Shah
2018-01-04 20:56 ` Theodore Ts'o
2018-01-04 21:16 ` Warner Losh
2018-01-04 22:55 ` Andy Kosela
2018-01-05 14:27 ` Clem Cole
2018-01-04 21:17 ` Bakul Shah
2018-01-04 17:20 ` Tom Ivar Helbekkmo
2018-01-04 17:28 ` Warner Losh
2018-01-03 17:07 ` Bakul Shah
-- strict thread matches above, loose matches on Subject: below --
2018-01-03 17:06 Norman Wilson
2018-01-03 7:53 Andy Kosela
2018-01-03 11:57 ` Ron Natalie
2018-01-03 14:22 ` Random832
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='CAP6exYJUvNuXi1o=wOX+cdkgLx-oDmttJTunzy5zsaMhLxd42g@mail.gmail.com' \
--to=rminnich@gmail.com \
/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).