public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	libc-alpha@sourceware.org, Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH v3 4/4] Remove set-hooks.h from generic includes
Date: Sat, 4 Mar 2023 12:42:34 -0500	[thread overview]
Message-ID: <612c3efb-4b53-e393-9c80-7cd76a59d4c9@redhat.com> (raw)
In-Reply-To: <20221227211145.3765256-5-adhemerval.zanella@linaro.org>

On 12/27/22 16:11, Adhemerval Zanella via Libc-alpha wrote:
> The hooks mechanism uses symbol sets for running lists of functions,
> which requires either extra linker directives to provide any hardening
> (such RELRO) or additional code (such as pointer obfuscation via

s/such/such as/g

> mangling with random value).

Please post v4.

Reviewed-by: Carlos O'Donell <carlos@redhat.com>

> 
> Currently only hurd uses it and there multiple examples where using
> direct function call provides both hardening and good code generation
> without the need to extra link or code handling.

Suggest:
Currently only hurd uses set-hooks.h so we remove it from the generic includes.
The generic implementation uses direct function calls which provide hardening
and good code generation, observability and debugging without the need for extra
linking options or special code handling.

> ---
>  {include => hurd}/set-hooks.h | 0
>  1 file changed, 0 insertions(+), 0 deletions(-)
>  rename {include => hurd}/set-hooks.h (100%)
> 
> diff --git a/include/set-hooks.h b/hurd/set-hooks.h
> similarity index 100%
> rename from include/set-hooks.h
> rename to hurd/set-hooks.h

-- 
Cheers,
Carlos.


  reply	other threads:[~2023-03-04 17:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27 21:11 [PATCH v3 0/4] Remove --with-default-link option Adhemerval Zanella
2022-12-27 21:11 ` [PATCH v3 1/4] Move libc_freeres_ptrs and libc_subfreeres to hidden/weak functions Adhemerval Zanella
2023-03-04 17:37   ` Carlos O'Donell
2022-12-27 21:11 ` [PATCH v3 2/4] libio: Remove the usage of __libc_IO_vtables Adhemerval Zanella
2023-03-04 17:37   ` Carlos O'Donell
2023-03-06 13:43     ` Adhemerval Zanella Netto
2023-03-27 12:53       ` Carlos O'Donell
2023-03-06 14:58   ` Arsen Arsenović
2023-03-06 16:01     ` Adhemerval Zanella Netto
2023-03-06 16:31       ` Andreas Schwab
2023-03-06 16:39         ` Adhemerval Zanella Netto
2023-03-06 16:53           ` Andreas Schwab
2023-03-06 17:24             ` Adhemerval Zanella Netto
2023-03-06 18:17               ` Adhemerval Zanella Netto
2023-03-06 18:47                 ` Arsen Arsenović
2023-03-06 18:53                   ` Adhemerval Zanella Netto
2023-03-06 19:10                     ` Arsen Arsenović
2023-03-06 19:20                       ` Adhemerval Zanella Netto
2023-03-06 19:26                         ` Arsen Arsenović
2023-03-06 16:23     ` Andreas Schwab
2022-12-27 21:11 ` [PATCH v3 3/4] Remove --with-default-link configure option Adhemerval Zanella
2023-03-04 17:39   ` Carlos O'Donell
2022-12-27 21:11 ` [PATCH v3 4/4] Remove set-hooks.h from generic includes Adhemerval Zanella
2023-03-04 17:42   ` Carlos O'Donell [this message]
2023-03-04 17:37 ` [PATCH v3 0/4] Remove --with-default-link option Carlos O'Donell
2023-03-06 13:43   ` Adhemerval Zanella Netto

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=612c3efb-4b53-e393-9c80-7cd76a59d4c9@redhat.com \
    --to=carlos@redhat.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).