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 v10 3/5] Fix assert during static startup (BZ 33326)
Date: Thu, 09 Jul 2026 15:00:06 +0200	[thread overview]
Message-ID: <lhu33xsz5bd.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20260623124831.2165041-4-adhemerval.zanella@linaro.org> (Adhemerval Zanella's message of "Tue, 23 Jun 2026 09:47:44 -0300")

* Adhemerval Zanella:

> diff --git a/elf/tst-assert-startup-static.c b/elf/tst-assert-startup-static.c
> new file mode 100644
> index 00000000000..66bc5d4913b
> --- /dev/null
> +++ b/elf/tst-assert-startup-static.c

> +/* The __tunables_init is called just before self-relocation and TLS setup,
> +   and the __libc_assert_fail is used internally for assert() calls.  */
> +extern _Noreturn __typeof (__assert_fail) __libc_assert_fail;
> +
> +void __tunables_init (char **env)
> +{
> +/* The assert called by the loader/startup issues __libc_assert_fail instead
> +   of __libc_assert, and __libc_assert_fail does issues the translation
> +   routines (which would require additional handling to be called at this
> +   point, like disable stack protection).  So issue the internal routine
> +   directly, instead of using assert here.  */
> +  __libc_assert_fail ("error", __FILE__, __LINE__, __func__);
> +}

There's some grammar issue here: “does issues the translation”

> diff --git a/sysdeps/generic/dl-mmap.h b/sysdeps/generic/dl-mmap.h
> new file mode 100644
> index 00000000000..f786be0930c
> --- /dev/null
> +++ b/sysdeps/generic/dl-mmap.h

> +/* This mmap call is used to allocate some memory to backup assert() messages
> +   before TLS setup is done (which setup the thread pointer used by some ABIs
> +   to issues syscalls).  */

typos: to back[ ]up
       which set[s ]up
       to [make] syscalls

(happens in other files, too)

sysdeps/unix/sysv/linux/i386/*.h uses t he phrase “to avoid use the
vDSO”.  It should be “to avoid using the vDSO” or “to avoid use of the
vDSO”.

> diff --git a/sysdeps/s390/string-bitops.h b/sysdeps/s390/string-bitops.h
> new file mode 100644
> index 00000000000..5527bcbe454
> --- /dev/null
> +++ b/sysdeps/s390/string-bitops.h
> @@ -0,0 +1,27 @@
> +/* Zero byte detection, define whether to use stdbit.h  s390 version.

Maybe: /* Zero byte detection control.  s390x version.

Thanks,
Florian


  reply	other threads:[~2026-07-09 13:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23 12:47 [PATCH v10 0/5] elf: Allow RPATH/RUNPATH for static-pie Adhemerval Zanella
2026-06-23 12:47 ` [PATCH v10 1/5] nptl: Add __raise_direct Adhemerval Zanella
2026-07-09 10:01   ` Florian Weimer
2026-07-09 12:46     ` Adhemerval Zanella Netto
2026-06-23 12:47 ` [PATCH v10 2/5] Use _dl_writev on __libc_message_impl Adhemerval Zanella
2026-06-23 12:47 ` [PATCH v10 3/5] Fix assert during static startup (BZ 33326) Adhemerval Zanella
2026-07-09 13:00   ` Florian Weimer [this message]
2026-06-23 12:47 ` [PATCH v10 4/5] elf: Allow RPATH/RUNPATH for static-pie " Adhemerval Zanella
2026-06-23 12:47 ` [PATCH v10 5/5] elf: Remove __chk_fail from dl-minimal.c Adhemerval Zanella
2026-07-09 10:03   ` 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=lhu33xsz5bd.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).