public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v3 2/2] Default to --with-default-link=no (bug 25812)
Date: Fri, 29 Apr 2022 16:03:03 +0200	[thread overview]
Message-ID: <87ilqs0yy0.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <e9f97b2a-3719-157c-e3cd-54c01aa72285@linaro.org> (Adhemerval Zanella's message of "Fri, 29 Apr 2022 10:55:47 -0300")

* Adhemerval Zanella:

> On 29/04/2022 10:17, Florian Weimer wrote:
>> * Adhemerval Zanella:
>> 
>>> On 11/04/2022 12:32, Florian Weimer via Libc-alpha wrote:
>>>> This is necessary to place the libio vtables into the RELRO segment.
>>>> New tests elf/tst-relro-ldso and elf/tst-relro-libc are added to
>>>> verify that this is what actually happens.
>>>>
>>>> The new tests fail on ia64 due to lack of (default) RELRO support
>>>> inbutils, so they are XFAILed there.
>>>
>>> I always frown upon new configure options, since they tend to degrade over
>>> time (as --disable-shared for instance [1]) and require additional 
>>> maintaining costs.  Why can't we make the required semantic the default 
>>> (since usually relro has minimal costs it a net gain in hardening)?
>> 
>> This is what the patch does, I think.
>
> I meant to not add --with-default-link= and just not use the extra linker 
> script.

That would be nice.  I want to get rid of the pointer arrays, and after
the vfprintf changes (and similar vscanf changes) are merged, we won't
need the vtable array anymore, either.  That should eliminate all
special section placement requirements.

Thanks,
Florian


  reply	other threads:[~2022-04-29 14:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 15:32 [PATCH v3 1/2] scripts: Add glibcelf.py module Florian Weimer
2022-04-11 15:32 ` [PATCH v3 2/2] Default to --with-default-link=no (bug 25812) Florian Weimer
2022-04-22  6:12   ` Siddhesh Poyarekar
2022-04-22  6:35     ` Florian Weimer
2022-04-22  8:12       ` Siddhesh Poyarekar
2022-04-22  8:24         ` Florian Weimer
2022-04-22  8:32           ` Siddhesh Poyarekar
2022-04-22  8:34             ` Florian Weimer
2022-04-22  8:36               ` Siddhesh Poyarekar
2022-04-22  8:56       ` Andreas Schwab
2022-04-29 16:02       ` Dmitry V. Levin
2022-04-29 16:14         ` Florian Weimer
2022-04-29 20:48           ` Dmitry V. Levin
2022-04-28  7:25   ` Fangrui Song
2022-04-28  8:40     ` Florian Weimer
2022-04-29  6:00       ` Fangrui Song
2022-04-29  7:09         ` Florian Weimer
2022-04-29  7:43           ` Fangrui Song
2022-04-29 14:55             ` Florian Weimer
2022-04-29 19:26               ` Fangrui Song
2022-04-29 12:59   ` Adhemerval Zanella
2022-04-29 13:17     ` Florian Weimer
2022-04-29 13:55       ` Adhemerval Zanella
2022-04-29 14:03         ` Florian Weimer [this message]
2022-04-21 15:54 ` [PATCH v3 1/2] scripts: Add glibcelf.py module Siddhesh Poyarekar
2022-04-21 20:23   ` 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=87ilqs0yy0.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --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).