From: Sam James <sam@gentoo.org>
To: Alejandro Colomar <alx.manpages@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, Sam James <sam@gentoo.org>
Subject: [PATCH] feature_test_macros.7: document -D_FORTIFY_SOURCE=3
Date: Thu, 13 Oct 2022 19:31:17 +0100 [thread overview]
Message-ID: <20221013183117.477592-1-sam@gentoo.org> (raw)
Reference: https://developers.redhat.com/blog/2021/04/16/broadening-compiler-checks-for-buffer-overflows-in-_fortify_source
Reference: https://developers.redhat.com/articles/2022/09/17/gccs-new-fortification-level
Signed-off-by: Sam James <sam@gentoo.org>
---
man7/feature_test_macros.7 | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/man7/feature_test_macros.7 b/man7/feature_test_macros.7
index d33041001..e62185745 100644
--- a/man7/feature_test_macros.7
+++ b/man7/feature_test_macros.7
@@ -643,9 +643,20 @@ and result in compiler warnings;
other checks take place at run time,
and result in a run-time error if the check fails.
.IP
+With
+.B _FORTIFY_SOURCE
+set to 3, additional checking is added to capture some function
+calls used with an argument of variable size.
+.IP
Use of this macro requires compiler support, available with
.BR gcc (1)
since version 4.0.
+.IP
+For use of
+.B _FORTIFY_SOURCE
+set to 3, then
+.BR gcc (1)
+version 12.0 or later is required.
.SS Default definitions, implicit definitions, and combining definitions
If no feature test macros are explicitly defined,
then the following feature test macros are defined by default:
--
2.38.0
next reply other threads:[~2022-10-13 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 18:31 Sam James [this message]
2022-10-13 18:50 ` [PATCH] feature_test_macros.7: document -D_FORTIFY_SOURCE=3 Alejandro Colomar
2022-10-13 18:57 ` Sam James
2022-10-13 19:12 ` Alejandro Colomar
2022-10-13 21:06 ` Sam James
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=20221013183117.477592-1-sam@gentoo.org \
--to=sam@gentoo.org \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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