public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
From: Stefan Liebler <stli@linux.ibm.com>
To: libc-stable@sourceware.org
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	Stefan Liebler via Libc-alpha <libc-alpha@sourceware.org>,
	Florian Weimer <fweimer@redhat.com>
Subject: [COMMITTED 2.34] S390: Enable static PIE
Date: Thu, 19 May 2022 17:20:07 +0200	[thread overview]
Message-ID: <62c0063c-ecbf-b795-e5be-e258accb04b9@linux.ibm.com> (raw)
In-Reply-To: <d74af583-94b5-7399-5fd9-7a2ffa0aea99@linux.ibm.com>

On 19/05/2022 09:49, Stefan Liebler wrote:
> On 04/05/2022 15:39, Florian Weimer wrote:
>> * Stefan Liebler:
>>
>>> 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?
>>
>> I think in isolation, it might break the Fedora builders and others.
>> I'll push the three approved patches today and repost the rest later
>> today.  Hopefully we can get this resolved by the end of this week.
>>
>> Thanks,
>> Florian
>>
> 
> This commit is now pushed to master and glibc 2.35 release branch
> (Florian's patch series is also already pushed to the release branch).
> 
> Thanks,
> Stefan

Also committed to glibc 2.34 release branch
(Florian's patch series is also already pushed to the release branch).

      reply	other threads:[~2022-05-19 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220428141530.567838-1-stli@linux.ibm.com>
     [not found] ` <87y1zk70vk.fsf@oldenburg.str.redhat.com>
     [not found]   ` <760241d4-2f3e-7078-ad98-a4d8ed3fdc69@linaro.org>
     [not found]     ` <87r15b4ubx.fsf@oldenburg.str.redhat.com>
     [not found]       ` <e69b03eb-0ee8-1cf5-b00a-e58a7720d8c2@linux.ibm.com>
     [not found]         ` <87pmkufx0s.fsf@oldenburg.str.redhat.com>
     [not found]           ` <25109979-63f6-2a8a-fe19-13bca2f42a6a@linux.ibm.com>
     [not found]             ` <87sfppquw8.fsf@oldenburg.str.redhat.com>
2022-05-19  7:49               ` [COMMITTED 2.35] " Stefan Liebler
2022-05-19 15:20                 ` Stefan Liebler [this message]

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=62c0063c-ecbf-b795-e5be-e258accb04b9@linux.ibm.com \
    --to=stli@linux.ibm.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-stable@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).