From: Richard Henderson <richard.henderson@linaro.org>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: berrange@redhat.com, i@maskray.me, philmd@redhat.com
Subject: Re: [PATCH 5/7] configure: Unnest detection of -z,relro and -z,now
Date: Wed, 18 Dec 2019 06:58:45 -1000 [thread overview]
Message-ID: <6a556fb0-619f-ffab-e9b3-5afb17447bee@linaro.org> (raw)
In-Reply-To: <881dff30-a729-6d7b-f823-5f136125ac0b@redhat.com>
On 12/17/19 10:11 PM, Thomas Huth wrote:
>> +# Detect support for DT_BIND_NOW.
>> +if compile_prog "" "-Wl,-z,now" ; then
>> + LDFLAGS="-Wl,-z,now $LDFLAGS"
>> +fi
>> +
>> +# Detect support for PT_GNU_RELRO.
>> +if compile_prog "" "-Wl,-z,relro" ; then
>> + LDFLAGS="-Wl,-z,relro $LDFLAGS"
>> +fi
>
> Looking at
> https://mudongliang.github.io/2016/07/11/relro-a-not-so-well-known-memory-corruption-mitigation-technique.html
> the idea of specifying these two options together was likely to get
> "Full RELRO" instead of only "Partial RELRO".
Sure.
> Thus, does it make sense to have "-Wl,-z,now" without "-Wl,-z,relro" in
> QEMU? Or should this rather check whether both are possible, then use
> both, otherwise just try to use "relro" alone?
Honestly, I expect them both to be supported in any binutils.
I split the two tests just because they didn't seem to be logically connected.
But I had forgotten about, or perhaps never heard, the terms "full" and
"partial" relro.
I can put them back together with an appropriate comment it you like. One less
thing to run during configure...
r~
next prev parent reply other threads:[~2019-12-18 16:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 3:19 [PATCH 0/7] configure: Improve PIE and other linkage Richard Henderson
2019-12-18 3:19 ` [PATCH 1/7] configure: Drop adjustment of textseg Richard Henderson
2019-12-18 6:59 ` Thomas Huth
2019-12-18 17:22 ` Richard Henderson
2019-12-18 3:19 ` [PATCH 2/7] tcg: Remove softmmu code_gen_buffer fixed address Richard Henderson
2019-12-18 7:01 ` Thomas Huth
2019-12-18 3:19 ` [PATCH 3/7] configure: Do not force pie=no for non-x86 Richard Henderson
2019-12-18 7:05 ` Thomas Huth
2019-12-18 19:23 ` Richard Henderson
2019-12-18 3:19 ` [PATCH 4/7] configure: Always detect -no-pie toolchain support Richard Henderson
2019-12-18 8:04 ` Thomas Huth
2019-12-18 17:55 ` Philippe Mathieu-Daudé
2019-12-18 3:19 ` [PATCH 5/7] configure: Unnest detection of -z,relro and -z,now Richard Henderson
2019-12-18 8:11 ` Thomas Huth
2019-12-18 16:58 ` Richard Henderson [this message]
2019-12-18 18:31 ` Thomas Huth
2019-12-18 3:19 ` [PATCH 6/7] configure: Override the os default with --disable-pie Richard Henderson
2019-12-18 8:13 ` Thomas Huth
2019-12-18 17:57 ` Philippe Mathieu-Daudé
2019-12-18 3:19 ` [PATCH 7/7] configure: Support -static-pie if requested Richard Henderson
2019-12-18 8:15 ` Thomas Huth
2019-12-18 7:28 ` [PATCH 0/7] configure: Improve PIE and other linkage Fangrui Song
2019-12-18 22:32 ` Richard Henderson
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=6a556fb0-619f-ffab-e9b3-5afb17447bee@linaro.org \
--to=richard.henderson@linaro.org \
--cc=berrange@redhat.com \
--cc=i@maskray.me \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).