From: Juergen Gross <jgross@suse.com>
To: Thomas Garnier <thgarnie@chromium.org>,
kernel-hardening@lists.openwall.com
Cc: kristen@linux.intel.com, Thomas Garnier <thgarnie@google.com>,
Alok Kataria <akataria@vmware.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 11/12] x86/paravirt: Adapt assembly for PIE support
Date: Mon, 27 May 2019 07:47:10 +0200 [thread overview]
Message-ID: <1b53b8eb-5dd3-fb57-d8db-06eedd0ce49f@suse.com> (raw)
In-Reply-To: <20190520231948.49693-12-thgarnie@chromium.org>
On 21/05/2019 01:19, Thomas Garnier wrote:
> From: Thomas Garnier <thgarnie@google.com>
>
> if PIE is enabled, switch the paravirt assembly constraints to be
> compatible. The %c/i constrains generate smaller code so is kept by
> default.
>
> Position Independent Executable (PIE) support will allow to extend the
> KASLR randomization range below 0xffffffff80000000.
>
> Signed-off-by: Thomas Garnier <thgarnie@google.com>
Acked-by: Juergen Gross <jgross@suse.com>
Juergen
next prev parent reply other threads:[~2019-05-27 5:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 23:19 [PATCH v7 00/12] x86: PIE support to extend KASLR randomization Thomas Garnier
2019-05-20 23:19 ` Thomas Garnier
2019-05-20 23:19 ` [PATCH v7 01/12] x86/crypto: Adapt assembly for PIE support Thomas Garnier
2019-05-21 4:06 ` Eric Biggers
2019-05-22 20:47 ` Thomas Garnier
2019-05-22 20:55 ` Eric Biggers
2019-05-29 15:48 ` Thomas Garnier
2019-05-20 23:19 ` [PATCH v7 02/12] x86: Use symbol name in jump table " Thomas Garnier
2019-05-20 23:23 ` Thomas Garnier
2019-05-20 23:19 ` [PATCH v7 03/12] x86: Add macro to get symbol address " Thomas Garnier
2019-05-21 3:12 ` hpa
2019-05-22 15:57 ` Thomas Garnier
2019-05-20 23:19 ` [PATCH v7 04/12] x86: relocate_kernel - Adapt assembly " Thomas Garnier
2019-06-10 21:33 ` Kees Cook
2019-05-20 23:19 ` [PATCH v7 05/12] x86/entry/64: " Thomas Garnier
2019-06-10 21:34 ` Kees Cook
2019-05-20 23:19 ` [PATCH v7 06/12] x86: pm-trace - " Thomas Garnier
2019-06-10 21:34 ` Kees Cook
2019-05-20 23:19 ` [PATCH v7 07/12] x86/CPU: " Thomas Garnier
2019-05-20 23:19 ` [PATCH v7 08/12] x86/acpi: " Thomas Garnier
2019-06-10 23:52 ` Kees Cook
2019-05-20 23:19 ` [PATCH v7 09/12] x86/boot/64: " Thomas Garnier
2019-06-10 22:26 ` Kees Cook
2019-05-20 23:19 ` [PATCH v7 10/12] x86/power/64: " Thomas Garnier
2019-06-10 23:52 ` Kees Cook
2019-05-20 23:19 ` [PATCH v7 11/12] x86/paravirt: " Thomas Garnier
2019-05-20 23:19 ` Thomas Garnier
2019-05-27 5:47 ` Juergen Gross
2019-05-27 5:47 ` Juergen Gross [this message]
2019-05-29 15:48 ` Thomas Garnier
2019-05-29 15:48 ` Thomas Garnier
2019-05-20 23:19 ` [PATCH v7 12/12] x86/alternatives: " Thomas Garnier
2019-06-10 21:32 ` [PATCH v7 00/12] x86: PIE support to extend KASLR randomization Kees Cook
2019-06-10 21:32 ` 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=1b53b8eb-5dd3-fb57-d8db-06eedd0ce49f@suse.com \
--to=jgross@suse.com \
--cc=akataria@vmware.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=kristen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=thgarnie@chromium.org \
--cc=thgarnie@google.com \
--cc=virtualization@lists.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 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.