From: Stefan Liebler <stli@linux.ibm.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Stefan Liebler via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] S390: Enable static PIE
Date: Wed, 4 May 2022 15:16:58 +0200 [thread overview]
Message-ID: <25109979-63f6-2a8a-fe19-13bca2f42a6a@linux.ibm.com> (raw)
In-Reply-To: <87pmkufx0s.fsf@oldenburg.str.redhat.com>
On 03/05/2022 17:36, Florian Weimer wrote:
> * Stefan Liebler:
>
>> I've just build glibc-HEAD and run the testsuite with
>> /proc/sys/kernel/randomize_va_space = 0. => Recognized fails as srbk failed.
>>
>> Then I've build with Florian's patch series on top. I don't see any
>> testsuite fails. Furthermore I've debbugged a static testcase into
>> _dl_early_allocate => mmap was used as result and previous was equal.
>>
>> With Florian's patch series also applied, static PIE binaries also run
>> on an unchanged kernel.
>
> That's great. Then I think this means it's safe to enable static PIE
> for s390x.
>
> Thanks,
> Florian
>
Thanks. Then I'll add some comments regarding your patch-series to
configure.ac before pushing.
Shall I wait until your patches are committed or is it okay if I push my
patch before?
next prev parent reply other threads:[~2022-05-04 13:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 14:15 Stefan Liebler
2022-05-02 9:13 ` Florian Weimer
2022-05-02 15:38 ` Adhemerval Zanella
2022-05-02 19:18 ` Florian Weimer
2022-05-03 12:56 ` Stefan Liebler
2022-05-03 15:36 ` Florian Weimer
2022-05-04 13:16 ` Stefan Liebler [this message]
2022-05-04 13:39 ` Florian Weimer
2022-05-19 7:49 ` [COMMITTED 2.35] " Stefan Liebler
2022-05-19 15:20 ` [COMMITTED 2.34] " Stefan Liebler
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=25109979-63f6-2a8a-fe19-13bca2f42a6a@linux.ibm.com \
--to=stli@linux.ibm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).