From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: "Frédéric Bérat" <fberat@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v2 00/14] Allow glibc to be built with _FORTIFY_SOURCE
Date: Mon, 26 Jun 2023 09:05:37 -0400 [thread overview]
Message-ID: <3cf6bf94-39c0-092a-3bcd-27960f0fce21@gotplt.org> (raw)
In-Reply-To: <20230623094223.3742673-1-fberat@redhat.com>
On 2023-06-23 05:42, Frédéric Bérat wrote:
> Hello,
>
> This patch series introduces a new "--enable-fortify-source" option to glibc
> build. This option may either be set to a value between 1 and 3, or left empty
> to let configure select the highest value available for the build system.
>
> The first patch adds the new configure option, the second excludes the routines
> that can't be built with the option enabled.
>
> The next patches are fixing test and compilation errors that arose with
> fortification enabled.
>
> I couldn't test the patch series in all configuration possible on all arches
> possible but I ran the following:
>
> - build-many-glibcs was executed on x86_64, for all arches/variants. This was
> mainly done to ensure that installed headers were not broken (as some
> patches are modifying system headers)
> - The new "enable-fortify-source" variant for BMG got executed on x86_64
> - make check and benchtests were executed on x86_64, i686, ppc64le, aarch64,
> s390x, with and without fortification enabled.
>
Patchwork CI seems to indicate that check-localplt is failing on
arm/aarch64. Could you please take a closer look?
https://patchwork.sourceware.org/project/glibc/patch/20230623094223.3742673-15-fberat@redhat.com/
Thanks,
Sid
next prev parent reply other threads:[~2023-06-26 13:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 9:42 Frédéric Bérat
2023-06-23 9:42 ` [PATCH v2 01/14] " Frédéric Bérat
2023-06-23 17:06 ` Joseph Myers
2023-06-23 9:42 ` [PATCH v2 02/14] Exclude routines from fortification Frédéric Bérat
2023-06-23 9:42 ` [PATCH v2 03/14] sysdeps: Ensure ieee128*_chk routines to be properly named Frédéric Bérat
2023-06-23 9:42 ` [PATCH v2 04/14] string: Ensure *_chk routines have their hidden builtin definition available Frédéric Bérat
2023-06-23 9:42 ` [PATCH v2 05/14] stdio: " Frédéric Bérat
2023-06-23 9:42 ` [PATCH v2 06/14] asprintf_chk: Ensure compatibility for both s390x and ppc64le Frédéric Bérat
2023-06-23 9:42 ` [PATCH v2 07/14] misc/sys/cdefs.h: Create FORTIFY redirects for internal calls Frédéric Bérat
2023-06-23 9:42 ` [PATCH v2 08/14] wcsmbs/bits/wchar2{,-decl}.h: Avoid PLT entries with _FORTIFY_SOURCE Frédéric Bérat
2023-06-23 9:42 ` [PATCH v2 09/14] posix/bits/unistd.h: Clearly separate declaration from definitions Frédéric Bérat
2023-06-23 9:42 ` [PATCH v2 10/14] posix/bits/unistd{,-decl}.h: Avoid PLT entries with _FORTIFY_SOURCE Frédéric Bérat
2023-06-23 9:42 ` [PATCH v2 11/14] misc/bits/select2.h: Clearly separate declaration from definitions Frédéric Bérat
2023-06-23 9:42 ` [PATCH v2 12/14] misc/bits/syslog.h: Clearly separate declaration from definition Frédéric Bérat
2023-06-23 9:42 ` [PATCH v2 13/14] sysdeps/ieee754/ldbl-128ibm-compat: Fix warn unused result Frédéric Bérat
2023-06-23 9:42 ` [PATCH v2 14/14] Add --enable-fortify-source option Frédéric Bérat
2023-06-26 13:05 ` Siddhesh Poyarekar [this message]
2023-06-26 15:28 ` [PATCH v2 00/14] Allow glibc to be built with _FORTIFY_SOURCE Frederic Berat
2023-06-27 11:07 ` Frederic Berat
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=3cf6bf94-39c0-092a-3bcd-27960f0fce21@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=fberat@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).