From: Sam James <sam@gentoo.org>
To: Mingye Wang <arthur200126@gmail.com>
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
linux-man@vger.kernel.org,
Erik Pilkington <erik.pilkington@gmail.com>
Subject: Re: [PATCH] feature_test_macros.7: document clang fortify support
Date: Thu, 23 Mar 2023 05:38:24 +0000 [thread overview]
Message-ID: <87pm90vxd3.fsf@gentoo.org> (raw)
In-Reply-To: <CAD66C+Y_b_9j1Oty=kbt2jZywzdVOen4i31ndhqyTTCRp=-xTg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
Mingye Wang <arthur200126@gmail.com> writes:
> Hi Alex,
>
> It looks like Sam James has already documented level 3 of the macro.
> The attached (no, git send-email is not happy with my proxy setup)
> patch only adds some language related to clang. Here's to hoping the
> system is happy with multipart mail.
>
> I've CCed Erik Pilington, since he is the author of the LLVM-svn
> 352665, the change that introduced __builtin_dynamic_object_size() in
> 2019.
>
The patch looks OK to me in terms of the content, apart from the libssp
mention. libssp and stack smashing protection overall is distinct from
fortification.
SSP is where stack canaries are emitted and their value is checked
later on to see if they're intact. Fortification is where certain
functions are replaced with variants that check the size of their
arguments e.g. dst & src and ensure they're big enough. They're distinct.
> Regards,
> Mingye Wang
>
> [2. text/x-patch; 0001-feature_test_macros.7-document-clang-fortify-support.patch]...
best,
sam
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
prev parent reply other threads:[~2023-03-23 5:40 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
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 ` Sam James [this message]
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=87pm90vxd3.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=alx.manpages@gmail.com \
--cc=arthur200126@gmail.com \
--cc=erik.pilkington@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