From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Cc: fweimer@redhat.com, jakub@redhat.com, Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [PATCH v7 1/4] Warn on unsupported fortification levels
Date: Thu, 31 Dec 2020 16:58:12 +0530 [thread overview]
Message-ID: <314a7fb5-c34f-e2cf-6bf7-beb630bb5a53@sourceware.org> (raw)
In-Reply-To: <df5a7689-ad16-5d30-9e61-ef5bfa3088f9@linaro.org>
On 12/31/20 4:15 PM, Adhemerval Zanella wrote:
>
>
> On 30/12/2020 03:43, Siddhesh Poyarekar wrote:
>> Make the _FORTIFY_SOURCE macro soup in features.h warn about
>> unsupported fortification levels. For example, it will warn about
>> _FORTIFY_SOURCE=3 and over with an indication of which level has been
>> selected.
>>
>> Co-authored-by: Paul Eggert <eggert@cs.ucla.edu>
>
> LGTM, although I think the NEWS entry should move to the second patch.
>
Oops, yes. I've moved the creatures.texi as well as NEWS content to 2/4
before commit.
Thanks,
Siddhesh
next prev parent reply other threads:[~2020-12-31 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 6:43 [PATCH v7 0/4] _FORTIFY_SOURCE=3 Siddhesh Poyarekar
2020-12-30 6:43 ` [PATCH v7 1/4] Warn on unsupported fortification levels Siddhesh Poyarekar
2020-12-31 10:45 ` Adhemerval Zanella
2020-12-31 11:28 ` Siddhesh Poyarekar [this message]
2020-12-30 6:43 ` [PATCH v7 2/4] Introduce _FORTIFY_SOURCE=3 Siddhesh Poyarekar
2020-12-31 10:47 ` Adhemerval Zanella
2020-12-30 6:43 ` [PATCH v7 3/4] string: Enable __FORTIFY_LEVEL=3 Siddhesh Poyarekar
2020-12-31 10:48 ` Adhemerval Zanella
2020-12-30 6:43 ` [PATCH v7 4/4] nonstring: " Siddhesh Poyarekar
2020-12-31 10:50 ` Adhemerval Zanella
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=314a7fb5-c34f-e2cf-6bf7-beb630bb5a53@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=jakub@redhat.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).