All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Emese Revfy <re.emese@gmail.com>
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>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [PATCH v4 1/3] GCC plugin infrastructure
Date: Tue, 1 Mar 2016 13:34:04 -0800	[thread overview]
Message-ID: <CAGXu5j+tUDi0zhYq4gdnLmX8EXyERX8+YaiTyTCqdP37je=O8w@mail.gmail.com> (raw)
In-Reply-To: <CAGXu5jKQUiZ0RQyMAKprWf30wMCXX7NvyfDLDgDz2zBqk-Xw6Q@mail.gmail.com>

On Tue, Mar 1, 2016 at 1:19 PM, Kees Cook <keescook@chromium.org> wrote:
> On Tue, Mar 1, 2016 at 9:15 AM, Emese Revfy <re.emese@gmail.com> wrote:
>> diff --git a/arch/Kconfig b/arch/Kconfig
>> index 155e6cd..4c54ef0 100644
>> --- a/arch/Kconfig
>> +++ b/arch/Kconfig
>> @@ -357,6 +357,19 @@ config SECCOMP_FILTER
>>
>>           See Documentation/prctl/seccomp_filter.txt for details.
>>
>> +config HAVE_GCC_PLUGINS
>> +       bool
>> +       help
>> +         An arch should select this symbol if it supports building with
>> +         GCC plugins.
>> +
>> +menuconfig GCC_PLUGINS
>> +       bool "GCC plugins"
>> +       depends on HAVE_GCC_PLUGINS
>> +       help
>> +         GCC plugins are loadable modules that provide extra features to the
>> +         compiler. They are useful for runtime instrumentation and static analysis.
>> +
>>  config HAVE_CC_STACKPROTECTOR
>>         bool
>>         help
>
> endmenu is missing?

Sorry, ignore my noise. However, my confusion does point on that maybe
gcc plugin config should live in tools/gcc/Kconfig and be included
here?

-Kees

-- 
Kees Cook
Chrome OS & Brillo Security

WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: Emese Revfy <re.emese@gmail.com>
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>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Fengguang Wu <fengguang.wu@intel.com>
Subject: [kernel-hardening] Re: [PATCH v4 1/3] GCC plugin infrastructure
Date: Tue, 1 Mar 2016 13:34:04 -0800	[thread overview]
Message-ID: <CAGXu5j+tUDi0zhYq4gdnLmX8EXyERX8+YaiTyTCqdP37je=O8w@mail.gmail.com> (raw)
In-Reply-To: <CAGXu5jKQUiZ0RQyMAKprWf30wMCXX7NvyfDLDgDz2zBqk-Xw6Q@mail.gmail.com>

On Tue, Mar 1, 2016 at 1:19 PM, Kees Cook <keescook@chromium.org> wrote:
> On Tue, Mar 1, 2016 at 9:15 AM, Emese Revfy <re.emese@gmail.com> wrote:
>> diff --git a/arch/Kconfig b/arch/Kconfig
>> index 155e6cd..4c54ef0 100644
>> --- a/arch/Kconfig
>> +++ b/arch/Kconfig
>> @@ -357,6 +357,19 @@ config SECCOMP_FILTER
>>
>>           See Documentation/prctl/seccomp_filter.txt for details.
>>
>> +config HAVE_GCC_PLUGINS
>> +       bool
>> +       help
>> +         An arch should select this symbol if it supports building with
>> +         GCC plugins.
>> +
>> +menuconfig GCC_PLUGINS
>> +       bool "GCC plugins"
>> +       depends on HAVE_GCC_PLUGINS
>> +       help
>> +         GCC plugins are loadable modules that provide extra features to the
>> +         compiler. They are useful for runtime instrumentation and static analysis.
>> +
>>  config HAVE_CC_STACKPROTECTOR
>>         bool
>>         help
>
> endmenu is missing?

Sorry, ignore my noise. However, my confusion does point on that maybe
gcc plugin config should live in tools/gcc/Kconfig and be included
here?

-Kees

-- 
Kees Cook
Chrome OS & Brillo Security

  reply	other threads:[~2016-03-01 21:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 17:14 [PATCH v4 0/3] Introduce GCC plugin infrastructure Emese Revfy
2016-03-01 17:14 ` [kernel-hardening] " Emese Revfy
2016-03-01 17:15 ` [PATCH v4 1/3] " Emese Revfy
2016-03-01 17:15   ` [kernel-hardening] " Emese Revfy
2016-03-01 19:07   ` Kees Cook
2016-03-01 19:07     ` [kernel-hardening] " Kees Cook
2016-03-02 20:57     ` Emese Revfy
2016-03-02 20:57       ` [kernel-hardening] " Emese Revfy
2016-03-01 21:19   ` Kees Cook
2016-03-01 21:19     ` [kernel-hardening] " Kees Cook
2016-03-01 21:34     ` Kees Cook [this message]
2016-03-01 21:34       ` Kees Cook
2016-03-02 21:18       ` Emese Revfy
2016-03-02 21:18         ` [kernel-hardening] " Emese Revfy
2016-03-01 22:50   ` Kees Cook
2016-03-01 22:50     ` [kernel-hardening] " Kees Cook
2016-03-02 21:33     ` PaX Team
2016-03-02 21:33       ` [kernel-hardening] " PaX Team
2016-03-01 17:16 ` [PATCH v4 2/3] Add Cyclomatic complexity GCC plugin Emese Revfy
2016-03-01 17:16   ` [kernel-hardening] " Emese Revfy
2016-03-01 17:17 ` [PATCH v4 3/3] Documentation for the GCC plugin infrastructure Emese Revfy
2016-03-01 17:17   ` [kernel-hardening] " Emese Revfy
2016-03-01 19:09 ` [PATCH v4 0/3] Introduce " Kees Cook
2016-03-01 19:09   ` [kernel-hardening] " Kees Cook
2016-03-01 19:16   ` Kees Cook
2016-03-01 19:16     ` [kernel-hardening] " Kees Cook

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='CAGXu5j+tUDi0zhYq4gdnLmX8EXyERX8+YaiTyTCqdP37je=O8w@mail.gmail.com' \
    --to=keescook@chromium.org \
    --cc=fengguang.wu@intel.com \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mmarek@suse.com \
    --cc=pageexec@freemail.hu \
    --cc=re.emese@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.