public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Mingye Wang <arthur200126@gmail.com>, linux-man@vger.kernel.org
Subject: Re: [PATCHv2] feature_test_macros.7: document clang fortify support
Date: Wed, 05 Apr 2023 02:53:33 +0100	[thread overview]
Message-ID: <87edozqekm.fsf@gentoo.org> (raw)
In-Reply-To: <6409b7ad-8b17-c2c4-9671-7c251cb93471@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]


Alejandro Colomar <alx.manpages@gmail.com> writes:

> [[PGP Signed Part:Undecided]]
> Hi Mingye,
>
> On 4/3/23 18:24, Mingye Wang wrote:
>> Hi Alex,
>> 
>> On Sat, Apr 1, 2023 at 5:56 AM Alejandro Colomar wrote:
>>> If it's just a reference to the software, that is fine.  If it's a
>>> reference to the version, then I want it to be greppable.
>>>
>> 
>> Is my patch attached to the last message all good, or is there
>> anything more to do?
>
> Sorry about the delay; I'm a bit overloaded.  Did you check Sam's
> objection?

I'm happy now after a clarification was made (libssp does more than I thought
it did).

>
> On 3/23/23 06:38, Sam James wrote:
>> 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.
>
> Thanks,
> Alex
>
>> 
>> Thanks,
>> Mingye


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]

  reply	other threads:[~2023-04-05  1:54 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 [this message]
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=87edozqekm.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=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