From: Emese Revfy <re.emese@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
PaX Team <pageexec@freemail.hu>,
Brad Spengler <spender@grsecurity.net>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Michal Marek <mmarek@suse.com>
Subject: [kernel-hardening] Re: [PATCH 2/3] Add Cyclomatic complexity GCC plugin
Date: Tue, 9 Feb 2016 19:55:32 +0100 [thread overview]
Message-ID: <20160209195532.fb72f47c5543cc0ada11653a@gmail.com> (raw)
In-Reply-To: <CAGXu5jJb4aJKQDTscJqUve6tO4S=5zU+X7ZGw87MfDoFMQSxLw@mail.gmail.com>
On Mon, 8 Feb 2016 20:23:12 -0800
Kees Cook <keescook@chromium.org> wrote:
> > + The complexity M of a function's control flow graph is defined as:
> > + M = E - N + 2P
> > + where
> > +
> > + E = the number of edges
> > + N = the number of nodes
> > + P = the number of connected components (exit nodes).
> > +
> > + See Documentation/gcc-plugins.txt for details.
>
> Is this plugin documented there? I don't see a chunk for that in this patch.
No yet, please see my other response.
--
Emese
next prev parent reply other threads:[~2016-02-09 18:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 21:27 [kernel-hardening] [PATCH 0/3] Introduce GCC plugin infrastructure Emese Revfy
2016-02-07 21:28 ` [kernel-hardening] [PATCH 1/3] " Emese Revfy
2016-02-08 20:28 ` [kernel-hardening] " Michal Marek
2016-02-08 21:31 ` Emese Revfy
2016-02-07 21:31 ` [kernel-hardening] [PATCH 2/3] Add Cyclomatic complexity GCC plugin Emese Revfy
2016-02-07 23:05 ` [kernel-hardening] " Rasmus Villemoes
2016-02-08 21:20 ` Emese Revfy
2016-02-09 4:23 ` Kees Cook
2016-02-09 18:55 ` Emese Revfy [this message]
2016-02-07 21:32 ` [kernel-hardening] [PATCH 3/3] Documentation for the GCC plugin infrastructure Emese Revfy
2016-02-09 4:27 ` [kernel-hardening] " Kees Cook
2016-02-09 19:14 ` Emese Revfy
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=20160209195532.fb72f47c5543cc0ada11653a@gmail.com \
--to=re.emese@gmail.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=pageexec@freemail.hu \
--cc=spender@grsecurity.net \
/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 NNTP newsgroup(s).