public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>,
	Siddhesh Poyarekar via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2 3/4] configure: Disable lazy binding by default
Date: Mon, 17 Jul 2023 10:57:44 -0400	[thread overview]
Message-ID: <f21298c0-b5ad-c267-e93b-826e1da90126@sourceware.org> (raw)
In-Reply-To: <87o7kgywvp.fsf@oldenburg.str.redhat.com>

On 2023-07-13 05:38, Florian Weimer via Libc-alpha wrote:
> * Siddhesh Poyarekar via Libc-alpha:
> 
>> +‘--disable-bind-now’
>> +     Enable lazy binding for installed shared objects and programs.
>> +     Lazy binding may improve program load times but it will disable
>> +     security hardening that enables full RELRO and a read-only global
>> +     offset table (GOT).
> 
> This description is not correct because as far as I can see,
> --disable-bind-now does not enable lazy binding if the toolchain or the
> build flags default to it.
> 
> I think we should remove this flag, rather than making
> --disable-bind-now work as documented.

I feel like this needs more thought either way then, no point blocking 
2.38 for it.  What's the use case for lazy binding?  Are people actually 
using this in the wild and would we be breaking things for them?

Thanks,
Sid

  reply	other threads:[~2023-07-17 14:59 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 18:41 [PATCH 0/4] Update default build configuration Siddhesh Poyarekar
2023-06-29 18:41 ` [PATCH 1/4] configure: Use autoconf 2.71 Siddhesh Poyarekar
2023-06-29 19:48   ` Joseph Myers
2023-06-29 19:56     ` Siddhesh Poyarekar
2023-06-29 20:03       ` Siddhesh Poyarekar
2023-06-29 20:07         ` Joseph Myers
2023-06-29 22:16           ` Zack Weinberg
2023-06-29 18:41 ` [PATCH 2/4] configure: Default --enable-stack-protector to strong Siddhesh Poyarekar
2023-06-29 18:41 ` [PATCH 3/4] Disable lazy binding by default Siddhesh Poyarekar
2023-06-29 21:54   ` Michael Hudson-Doyle
2023-06-29 22:16     ` Siddhesh Poyarekar
2023-06-29 18:41 ` [PATCH 4/4] configure: Disable building libcrypt " Siddhesh Poyarekar
2023-06-29 18:45   ` Dmitry V. Levin
2023-06-29 19:02     ` Siddhesh Poyarekar
2023-07-14  6:21   ` Sam James
2023-07-17 15:24     ` Siddhesh Poyarekar
2023-07-17 17:26       ` Sam James
2023-06-30  1:42 ` [PATCH v2 0/4] Update default build configuration Siddhesh Poyarekar
2023-06-30  1:42   ` [PATCH v2 1/4] configure: Use autoconf 2.71 Siddhesh Poyarekar
2023-07-14 21:00     ` Carlos O'Donell
2023-07-17 14:21     ` [PATCH v3] " Siddhesh Poyarekar
2023-07-17 14:46       ` Siddhesh Poyarekar
2023-06-30  1:42   ` [PATCH v2 2/4] configure: Default --enable-stack-protector to strong Siddhesh Poyarekar
2023-07-13  9:51     ` Florian Weimer
2023-07-17 14:55       ` Siddhesh Poyarekar
2023-07-17 15:45         ` Florian Weimer
2023-07-17 15:52           ` Siddhesh Poyarekar
2023-08-03 10:06             ` Florian Weimer
2023-06-30  1:42   ` [PATCH v2 3/4] configure: Disable lazy binding by default Siddhesh Poyarekar
2023-07-13  9:38     ` Florian Weimer
2023-07-17 14:57       ` Siddhesh Poyarekar [this message]
2023-07-17 15:30         ` Florian Weimer
2023-07-17 15:55           ` Siddhesh Poyarekar
2023-07-18 16:25             ` Andreas K. Huettel
2023-06-30  1:42   ` [PATCH v2 4/4] configure: Disable building libcrypt " Siddhesh Poyarekar
2023-07-13  9:40     ` Florian Weimer
2023-07-14  4:16     ` Mark Harris
2023-07-17 15:13       ` Siddhesh Poyarekar
2023-07-17 16:44     ` [PATCH v3] " Siddhesh Poyarekar
2023-07-17 17:18       ` Andreas Schwab
2023-07-17 18:17         ` Siddhesh Poyarekar
2023-07-20 18:05       ` Joseph Myers
2023-07-20 18:39         ` Andreas K. Huettel
2023-07-07 10:31   ` [ping][PATCH v2 0/4] Update default build configuration Siddhesh Poyarekar
2023-07-12 21:51   ` [ping2][PATCH " Siddhesh Poyarekar

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=f21298c0-b5ad-c267-e93b-826e1da90126@sourceware.org \
    --to=siddhesh@sourceware.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).