From: Daniel Micay <danielmicay@gmail.com>
To: kernel-hardening@lists.openwall.com, Kees Cook <keescook@chromium.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [kernel-hardening] Self Introduction
Date: Thu, 10 Dec 2015 18:04:04 -0500 [thread overview]
Message-ID: <1449788644.8579.27.camel@gmail.com> (raw)
In-Reply-To: <5669FEE1.8812.1230AD@pageexec.freemail.hu>
[-- Attachment #1: Type: text/plain, Size: 214 bytes --]
> uhm, what races? the per-cpu PGD exists for that reason, regardless of
> PCID.
Ah, that makes sense. So the non-strong PCID UDEREF is really just
hardware acceleration for what you were already doing before.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-12-10 23:04 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 17:21 [kernel-hardening] Self Introduction David Brown
2015-12-09 22:19 ` Kees Cook
2015-12-10 0:00 ` David Brown
2015-12-10 0:14 ` Kees Cook
2015-12-10 0:26 ` David Brown
2015-12-10 0:41 ` Kees Cook
2015-12-10 17:14 ` Stephen Smalley
2015-12-10 17:49 ` Kees Cook
2015-12-10 17:55 ` Daniel Micay
2015-12-10 18:42 ` Kees Cook
2015-12-10 19:07 ` Daniel Micay
2015-12-10 19:23 ` Kees Cook
2015-12-10 19:38 ` Schaufler, Casey
2015-12-10 19:45 ` Kees Cook
2015-12-11 17:54 ` Valdis.Kletnieks
2015-12-11 18:44 ` Kees Cook
2015-12-12 11:40 ` Heiko Carstens
2015-12-10 22:38 ` PaX Team
2015-12-10 23:04 ` Daniel Micay [this message]
2015-12-10 18:42 ` Catalin Marinas
2015-12-10 18:47 ` Kees Cook
2015-12-10 23:52 ` Kees Cook
2015-12-11 1:04 ` David Brown
2016-01-11 18:33 ` David Brown
2016-01-12 19:31 ` Kees Cook
2016-01-13 11:29 ` Catalin Marinas
2016-01-13 11:31 ` Catalin Marinas
2016-01-14 1:04 ` Ben Hutchings
2016-01-14 11:11 ` Catalin Marinas
2016-10-09 12:34 [kernel-hardening] self introduction Colin Vidal
2016-10-09 14:04 ` David Windsor
2016-10-09 19:09 ` Colin Vidal
2016-10-09 19:37 ` Jann Horn
2016-10-10 6:02 ` Reshetova, Elena
2016-10-10 16:01 ` Colin Vidal
2016-10-10 17:01 ` Reshetova, Elena
2016-10-10 21:05 ` Kees Cook
2016-10-12 3:19 ` Gengjia Chen
2016-10-12 22:31 ` Kees Cook
2016-10-13 11:14 ` Gengjia Chen
2016-10-13 18:50 ` Kees Cook
2016-10-17 11:57 ` Gengjia Chen
2016-10-17 20:15 ` Kees Cook
2016-10-18 11:52 ` Gengjia Chen
2016-10-18 21:21 ` Kees Cook
2016-10-12 8:25 ` Colin Vidal
2016-10-12 22:35 ` Kees Cook
2016-10-13 13:54 ` Reshetova, Elena
2016-10-13 18:53 ` Kees Cook
2016-10-13 19:26 ` Hans Liljestrand
2016-10-10 20:57 ` Kees Cook
2016-10-12 8:27 ` Colin Vidal
2016-10-12 22:40 ` Kees Cook
2016-10-14 18:32 ` Andy Lutomirski
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=1449788644.8579.27.camel@gmail.com \
--to=danielmicay@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.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 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.