From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: fanquake <fanquake@gmail.com>,
libc-alpha@sourceware.org, Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH] doc: correct _FORTIFY_SOURCE doc in features.h
Date: Tue, 31 Jan 2023 09:20:42 -0500 [thread overview]
Message-ID: <65bcd2c4-3f0f-12f3-fc06-c476662e6f51@gotplt.org> (raw)
In-Reply-To: <20230131132510.98243-1-fanquake@gmail.com>
Thanks, that looks correct. Carlos, may I push this before you cut the
release?
Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
On 2023-01-31 08:25, fanquake via Libc-alpha wrote:
> ---
> include/features.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/features.h b/include/features.h
> index 7d2c7a4f87..07c73b3e55 100644
> --- a/include/features.h
> +++ b/include/features.h
> @@ -57,7 +57,8 @@
> __STRICT_ANSI__).
>
> _FORTIFY_SOURCE Add security hardening to many library functions.
> - Set to 1 or 2; 2 performs stricter checks than 1.
> + Set to 1, 2 or 3; 3 performs stricter checks than 2, which
> + performs stricter checks than 1.
>
> _REENTRANT, _THREAD_SAFE
> Obsolete; equivalent to _POSIX_C_SOURCE=199506L.
next prev parent reply other threads:[~2023-01-31 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 13:25 fanquake
2023-01-31 14:20 ` Siddhesh Poyarekar [this message]
2023-01-31 20:29 ` Carlos O'Donell
2023-01-31 22:34 ` 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=65bcd2c4-3f0f-12f3-fc06-c476662e6f51@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=fanquake@gmail.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).