From: Alejandro Colomar <alx.manpages@gmail.com>
To: Mingye Wang <arthur200126@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: Request to update feature_test_macros(7) wrt FORTIFY_SOURCE
Date: Mon, 20 Mar 2023 09:47:58 +0100 [thread overview]
Message-ID: <6c5593f5-efc0-564d-83fa-430328b31231@gmail.com> (raw)
In-Reply-To: <CAD66C+aECcWHSogwDygQnHOvDCayHbH2emKrsUhVxkg48KzXfA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1539 bytes --]
Hi Mingye,
On 3/20/23 09:15, Mingye Wang wrote:
> Hi,
>
> It might be a good time to update the _FORTIFY_SOURCE bit in the
> f_t_m(7) manpage. Specifically:
>
> We currently have it stuck at level 2. Since level 3 is now a thing in
> gcc and clang with the introduction of __builtin_dynamic_object_size,
> we should add it. The language should be similar to the level 2
> description, with the difference that level 3 is able to evalulate
> dynamic sizes. There are two articles from Redhat about this new
> level: one from when only clang had it[1], and the other from when gcc
> added it too.[2].
> [1]: https://developers.redhat.com/blog/2021/04/16/broadening-compiler-checks-for-buffer-overflows-in-_fortify_source#in_the_very_long_term__everything_is_dynamic
> [2]: https://developers.redhat.com/articles/2022/09/17/gccs-new-fortification-level
>
> The other point relates to clang, in that we should mention that it
> has it too since svn revision 55735 (2008). I will take some time to
> track down the released version number. We also need to mention when
> gcc and clang added the level 3 stuff.
>
> I plan to send a patch on this stuff, but do be warned my man(7) and
> git send-email are very rusty.
Thanks! No problem about that. Please CC some GCC or Clang mailing
list and related developers when you send your patch.
Cheers,
Alex
>
> Regards,
> Mingye Wang (Artoria2e5)
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-03-20 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 8:15 Request to update feature_test_macros(7) wrt FORTIFY_SOURCE Mingye Wang
2023-03-20 8:47 ` Alejandro Colomar [this message]
2023-03-22 8:39 ` [PATCH] feature_test_macros.7: document clang fortify support Mingye Wang
2023-03-22 17:19 ` Alejandro Colomar
2023-03-24 6:07 ` [PATCHv2] " Mingye Wang
2023-03-31 21:56 ` Alejandro Colomar
2023-04-03 16:24 ` Mingye Wang
2023-04-05 1:32 ` Alejandro Colomar
2023-04-05 1:53 ` Sam James
2023-04-05 2:21 ` Alejandro Colomar
2023-03-23 5:38 ` [PATCH] " 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=6c5593f5-efc0-564d-83fa-430328b31231@gmail.com \
--to=alx.manpages@gmail.com \
--cc=arthur200126@gmail.com \
--cc=linux-man@vger.kernel.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