From: "H. Peter Anvin" <hpa@zytor.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Jarkko Sakkinen <jarkko.sakkinen@intel.com>,
Matthew Garrett <mjg@redhat.com>,
Matt Fleming <matt.fleming@intel.com>,
Eric Northup <digitaleric@google.com>,
Dan Rosenberg <drosenberg@vsecurity.com>,
Julien Tinnes <jln@google.com>, Will Drewry <wad@chromium.org>
Subject: Re: [PATCH 2/6] x86: kaslr: move CPU flags out of cpucheck
Date: Thu, 25 Apr 2013 15:00:55 -0700 [thread overview]
Message-ID: <5179A797.9040200@zytor.com> (raw)
In-Reply-To: <1366926860-26776-3-git-send-email-keescook@chromium.org>
On 04/25/2013 02:54 PM, Kees Cook wrote:
> Since has_eflag() and has_fpu() are 32-bit only, short-circuit the
> routines on 64-bit when they are built without -m32. This also refactors
> the calls to cpuid to make them PIC-safe on 32-bit.
These functions can trivially be made 32- and 64-bit agnostic by
changing "u32" to "unsigned long" and drop the -l suffixes in the
assembly code.
-hpa
next prev parent reply other threads:[~2013-04-25 22:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 21:54 [PATCH v3 0/6] kernel ASLR Kees Cook
2013-04-25 21:54 ` [PATCH 1/6] x86: kaslr: move ELF relocation handling to C Kees Cook
2013-04-25 21:54 ` [PATCH 2/6] x86: kaslr: move CPU flags out of cpucheck Kees Cook
2013-04-25 22:00 ` H. Peter Anvin [this message]
2013-04-26 15:28 ` Kees Cook
2013-04-25 21:54 ` [PATCH 3/6] x86: kaslr: return location from decompress_kernel Kees Cook
2013-04-25 21:54 ` [PATCH 4/6] x86: kaslr: select random base offset Kees Cook
2013-04-26 6:13 ` [kernel-hardening] " Mathias Krause
2013-04-26 15:30 ` Kees Cook
2013-04-25 21:54 ` [PATCH 5/6] x86: kaslr: select memory region from e820 maps Kees Cook
2013-04-25 21:54 ` [PATCH 6/6] x86: kaslr: report kernel offset on panic Kees Cook
2013-04-25 22:01 ` [PATCH v3 0/6] kernel ASLR H. Peter Anvin
2013-04-26 18:53 ` Kees Cook
-- strict thread matches above, loose matches on Subject: below --
2013-04-26 19:03 [PATCH v4 " Kees Cook
2013-04-26 19:03 ` [PATCH 2/6] x86: kaslr: move CPU flags out of cpucheck Kees Cook
2013-04-26 21:47 ` H. Peter Anvin
2013-04-26 22:14 ` H. Peter Anvin
2013-04-29 17:49 ` Kees Cook
2013-04-29 17:52 ` Kees Cook
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=5179A797.9040200@zytor.com \
--to=hpa@zytor.com \
--cc=digitaleric@google.com \
--cc=drosenberg@vsecurity.com \
--cc=jarkko.sakkinen@intel.com \
--cc=jln@google.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=mjg@redhat.com \
--cc=tglx@linutronix.de \
--cc=wad@chromium.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