From: Joseph Myers <joseph@codesourcery.com>
To: "Frédéric Bérat" <fberat@redhat.com>
Cc: <libc-alpha@sourceware.org>, <siddhesh@gotplt.org>
Subject: Re: [PATCH v2 01/14] Allow glibc to be built with _FORTIFY_SOURCE
Date: Fri, 23 Jun 2023 17:06:42 +0000 [thread overview]
Message-ID: <bad18d1-8257-68a-4781-71a35ef7756@codesourcery.com> (raw)
In-Reply-To: <20230623094223.3742673-2-fberat@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
On Fri, 23 Jun 2023, Frédéric Bérat via Libc-alpha wrote:
> diff --git a/NEWS b/NEWS
> index 709ee40e50..027506a44c 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -502,6 +502,9 @@ Major new features:
> * The audit libraries will avoid unnecessary slowdown if it is not required
> PLT tracking (by not implementing the la_pltenter or la_pltexit callbacks).
>
> +* Glibc now supports to be built with _FORTIFY_SOURCE. The value is undefined
> + for parts of the library that can't be built with it.
> +
This is the NEWS section for 2.35. You need to put this entry in the
section for 2.38 (and remember to move to the section for 2.39 if these
changes don't make it into 2.38).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-06-23 17:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 9:42 [PATCH v2 00/14] " 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 [this message]
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 ` [PATCH v2 00/14] Allow glibc to be built with _FORTIFY_SOURCE Siddhesh Poyarekar
2023-06-26 15:28 ` 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=bad18d1-8257-68a-4781-71a35ef7756@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=fberat@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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).