From: Shuah Khan <shuah@kernel.org>
To: Florian Weimer <fweimer@redhat.com>,
linux-x86_64@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-arch@vger.kernel.org, x86@kernel.org
Cc: rdunlap@infradead.org, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] selftests/x86: Detect -no-pie availability
Date: Fri, 4 May 2018 13:39:33 -0600 [thread overview]
Message-ID: <f55777ec-53e5-ad7a-dca9-6313dc779342@kernel.org> (raw)
In-Reply-To: <20180502121433.7F874401F1BF7@oldenburg.str.redhat.com>
On 05/02/2018 06:10 AM, Florian Weimer wrote:
> Some toolchains need -no-pie to build all tests, others do not support
> the -no-pie flag at all. Therefore, add another test for the
> availability of the flag.
>
> This amends commit 3346a6a4e5ba8c040360f753b26938cec31a4bdc
> ("selftests: x86: sysret_ss_attrs doesn't build on a PIE build").
>
> Signed-off-by: Florian Weimer <fweimer@redhat.com>
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
> Tested-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> tools/testing/selftests/x86/Makefile | 8 +++++++-
> tools/testing/selftests/x86/trivial_program.c | 10 ++++++++++
> 2 files changed, 17 insertions(+), 1 deletion(-)
> create mode 100644 tools/testing/selftests/x86/trivial_program.c
>
> diff --git a/tools/testing/selftests/x86/Makefile b/tools/testing/selftests/x86/Makefile
> index d744991c0f4f..94c89261a236 100644
> --- a/tools/testing/selftests/x86/Makefile
> +++ b/tools/testing/selftests/x86/Makefile
> @@ -8,6 +8,7 @@ include ../lib.mk
> UNAME_M := $(shell uname -m)
> CAN_BUILD_I386 := $(shell ./check_cc.sh $(CC) trivial_32bit_program.c -m32)
> CAN_BUILD_X86_64 := $(shell ./check_cc.sh $(CC) trivial_64bit_program.c)
> +CAN_BUILD_WITH_NOPIE := $(shell ./check_cc.sh $(CC) trivial_program.c -no-pie)
>
> TARGETS_C_BOTHBITS := single_step_syscall sysret_ss_attrs syscall_nt test_mremap_vdso \
> check_initial_reg_state sigreturn iopl mpx-mini-test ioperm \
> @@ -31,7 +32,12 @@ BINARIES_64 := $(TARGETS_C_64BIT_ALL:%=%_64)
> BINARIES_32 := $(patsubst %,$(OUTPUT)/%,$(BINARIES_32))
> BINARIES_64 := $(patsubst %,$(OUTPUT)/%,$(BINARIES_64))
>
> -CFLAGS := -O2 -g -std=gnu99 -pthread -Wall -no-pie
> +CFLAGS := -O2 -g -std=gnu99 -pthread -Wall
> +
> +# call32_from_64 in thunks.S uses absolute addresses.
> +ifeq ($(CAN_BUILD_WITH_NOPIE),1)
> +CFLAGS += -no-pie
> +endif
>
> define gen-target-rule-32
> $(1) $(1)_32: $(OUTPUT)/$(1)_32
> diff --git a/tools/testing/selftests/x86/trivial_program.c b/tools/testing/selftests/x86/trivial_program.c
> new file mode 100644
> index 000000000000..46a447163b93
> --- /dev/null
> +++ b/tools/testing/selftests/x86/trivial_program.c
> @@ -0,0 +1,10 @@
> +/* Trivial program to check that compilation with certain flags is working. */
> +
> +#include <stdio.h>
> +
> +int
> +main(void)
> +{
> + puts("");
> + return 0;
> +}
>
Thanks. I will queue this up for 4.18-rc1
thahnks,
-- Shuah
next prev parent reply other threads:[~2018-05-04 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 12:10 [PATCH] selftests/x86: Detect -no-pie availability Florian Weimer
2018-05-04 19:39 ` Shuah Khan [this message]
2018-05-10 17:30 ` Shuah Khan
-- strict thread matches above, loose matches on Subject: below --
2018-02-26 14:31 Florian Weimer
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=f55777ec-53e5-ad7a-dca9-6313dc779342@kernel.org \
--to=shuah@kernel.org \
--cc=fweimer@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-x86_64@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).