From: Emese Revfy <re.emese@gmail.com>
To: Laura Abbott <labbott@redhat.com>
Cc: linux-kbuild@vger.kernel.org, pageexec@freemail.hu,
spender@grsecurity.net, kernel-hardening@lists.openwall.com,
mmarek@suse.com, keescook@chromium.org, linux@rasmusvillemoes.dk,
fengguang.wu@intel.com, dvyukov@google.com,
linux-kernel@vger.kernel.org, david.brown@linaro.org,
yamada.masahiro@socionext.com
Subject: Re: [PATCH v9 3/4] Add Cyclomatic complexity GCC plugin
Date: Wed, 15 Jun 2016 00:33:06 +0200 [thread overview]
Message-ID: <20160615003306.9f92b6244b7c862cca07b5e5@gmail.com> (raw)
In-Reply-To: <041e2196-2213-725d-64aa-8526b23bc618@redhat.com>
On Tue, 14 Jun 2016 12:29:59 -0700
Laura Abbott <labbott@redhat.com> wrote:
> This has some weird interaction with ftrace. On x86
>
> 1) make mrproper
> 2) make defconfig
> 3) enable GCC_PLUGINS, GCC_PLUGIN_CYC_COMPLEXITY
> 4) enable FUNCTION_TRACER (it will select other options as well)
> 5) make && make modules
>
> MODPOST 18 modules
> ERROR: "__fentry__" [net/netfilter/xt_nat.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/xt_mark.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/xt_addrtype.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/xt_LOG.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/nf_nat_sip.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/nf_nat_irc.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/nf_nat_ftp.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/nf_nat.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/nf_log_common.ko] undefined!
> ERROR: "__fentry__" [net/ipv6/netfilter/nf_log_ipv6.ko] undefined!
> ERROR: "__fentry__" [net/ipv4/netfilter/nf_nat_masquerade_ipv4.ko] undefined!
> ERROR: "__fentry__" [net/ipv4/netfilter/nf_nat_ipv4.ko] undefined!
> ERROR: "__fentry__" [net/ipv4/netfilter/nf_log_ipv4.ko] undefined!
> ERROR: "__fentry__" [net/ipv4/netfilter/nf_log_arp.ko] undefined!
> ERROR: "__fentry__" [net/ipv4/netfilter/iptable_nat.ko] undefined!
> ERROR: "__fentry__" [net/ipv4/netfilter/ipt_MASQUERADE.ko] undefined!
> ERROR: "__fentry__" [fs/efivarfs/efivarfs.ko] undefined!
> ERROR: "__fentry__" [drivers/thermal/x86_pkg_temp_thermal.ko] undefined!
> scripts/Makefile.modpost:91: recipe for target '__modpost' failed
> make[1]: *** [__modpost] Error 1
>
> Verified with gcc-5.3.1 and gcc-6.1.1. You need to do a clean build
> with 'make mrproper' first to see this. Subsequent builds will
> succeed oddly enough. I suspect this
Thanks for the report, I'm looking into it.
--
Emese
WARNING: multiple messages have this Message-ID (diff)
From: Emese Revfy <re.emese@gmail.com>
To: Laura Abbott <labbott@redhat.com>
Cc: linux-kbuild@vger.kernel.org, pageexec@freemail.hu,
spender@grsecurity.net, kernel-hardening@lists.openwall.com,
mmarek@suse.com, keescook@chromium.org, linux@rasmusvillemoes.dk,
fengguang.wu@intel.com, dvyukov@google.com,
linux-kernel@vger.kernel.org, david.brown@linaro.org,
yamada.masahiro@socionext.com
Subject: [kernel-hardening] Re: [PATCH v9 3/4] Add Cyclomatic complexity GCC plugin
Date: Wed, 15 Jun 2016 00:33:06 +0200 [thread overview]
Message-ID: <20160615003306.9f92b6244b7c862cca07b5e5@gmail.com> (raw)
In-Reply-To: <041e2196-2213-725d-64aa-8526b23bc618@redhat.com>
On Tue, 14 Jun 2016 12:29:59 -0700
Laura Abbott <labbott@redhat.com> wrote:
> This has some weird interaction with ftrace. On x86
>
> 1) make mrproper
> 2) make defconfig
> 3) enable GCC_PLUGINS, GCC_PLUGIN_CYC_COMPLEXITY
> 4) enable FUNCTION_TRACER (it will select other options as well)
> 5) make && make modules
>
> MODPOST 18 modules
> ERROR: "__fentry__" [net/netfilter/xt_nat.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/xt_mark.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/xt_addrtype.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/xt_LOG.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/nf_nat_sip.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/nf_nat_irc.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/nf_nat_ftp.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/nf_nat.ko] undefined!
> ERROR: "__fentry__" [net/netfilter/nf_log_common.ko] undefined!
> ERROR: "__fentry__" [net/ipv6/netfilter/nf_log_ipv6.ko] undefined!
> ERROR: "__fentry__" [net/ipv4/netfilter/nf_nat_masquerade_ipv4.ko] undefined!
> ERROR: "__fentry__" [net/ipv4/netfilter/nf_nat_ipv4.ko] undefined!
> ERROR: "__fentry__" [net/ipv4/netfilter/nf_log_ipv4.ko] undefined!
> ERROR: "__fentry__" [net/ipv4/netfilter/nf_log_arp.ko] undefined!
> ERROR: "__fentry__" [net/ipv4/netfilter/iptable_nat.ko] undefined!
> ERROR: "__fentry__" [net/ipv4/netfilter/ipt_MASQUERADE.ko] undefined!
> ERROR: "__fentry__" [fs/efivarfs/efivarfs.ko] undefined!
> ERROR: "__fentry__" [drivers/thermal/x86_pkg_temp_thermal.ko] undefined!
> scripts/Makefile.modpost:91: recipe for target '__modpost' failed
> make[1]: *** [__modpost] Error 1
>
> Verified with gcc-5.3.1 and gcc-6.1.1. You need to do a clean build
> with 'make mrproper' first to see this. Subsequent builds will
> succeed oddly enough. I suspect this
Thanks for the report, I'm looking into it.
--
Emese
next prev parent reply other threads:[~2016-06-14 22:26 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 22:07 [PATCH v9 0/4] Introduce GCC plugin infrastructure Emese Revfy
2016-05-23 22:07 ` [kernel-hardening] " Emese Revfy
2016-05-23 22:08 ` [PATCH v9 1/4] Shared library support Emese Revfy
2016-05-23 22:08 ` [kernel-hardening] " Emese Revfy
2016-05-23 22:09 ` [PATCH v9 2/4] GCC plugin infrastructure Emese Revfy
2016-05-23 22:09 ` [kernel-hardening] " Emese Revfy
2016-05-23 22:10 ` [PATCH v9 3/4] Add Cyclomatic complexity GCC plugin Emese Revfy
2016-05-23 22:10 ` [kernel-hardening] " Emese Revfy
2016-06-14 19:29 ` Laura Abbott
2016-06-14 19:29 ` [kernel-hardening] " Laura Abbott
2016-06-14 22:33 ` Emese Revfy [this message]
2016-06-14 22:33 ` Emese Revfy
2016-06-15 20:53 ` Emese Revfy
2016-06-15 20:53 ` [kernel-hardening] " Emese Revfy
2016-06-15 22:41 ` Kees Cook
2016-06-15 22:41 ` [kernel-hardening] " Kees Cook
2016-06-15 22:41 ` Kees Cook
2016-05-23 22:11 ` [PATCH v9 4/4] Add sancov plugin Emese Revfy
2016-05-23 22:11 ` [kernel-hardening] " Emese Revfy
2016-05-24 17:04 ` [PATCH v9 0/4] Introduce GCC plugin infrastructure Kees Cook
2016-05-24 17:04 ` [kernel-hardening] " Kees Cook
2016-05-24 17:04 ` Kees Cook
2016-05-25 10:46 ` Michal Marek
2016-05-25 10:46 ` [kernel-hardening] " Michal Marek
2016-05-25 10:46 ` Michal Marek
2016-05-25 17:12 ` Kees Cook
2016-05-25 17:12 ` [kernel-hardening] " Kees Cook
2016-05-25 17:12 ` Kees Cook
2016-06-07 20:58 ` Michal Marek
2016-06-07 20:58 ` [kernel-hardening] " Michal Marek
2016-06-07 20:58 ` Michal Marek
2016-06-07 20:59 ` Kees Cook
2016-06-07 20:59 ` [kernel-hardening] " Kees Cook
2016-06-07 20:59 ` Kees Cook
2016-06-07 21:59 ` Emese Revfy
2016-06-07 21:59 ` [kernel-hardening] " Emese Revfy
2016-06-07 21:59 ` Emese Revfy
2016-06-07 21:58 ` Kees Cook
2016-06-07 21:58 ` [kernel-hardening] " Kees Cook
2016-06-07 21:58 ` Kees Cook
2016-06-08 6:59 ` Michal Marek
2016-06-08 6:59 ` [kernel-hardening] " Michal Marek
2016-06-08 6:59 ` Michal Marek
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=20160615003306.9f92b6244b7c862cca07b5e5@gmail.com \
--to=re.emese@gmail.com \
--cc=david.brown@linaro.org \
--cc=dvyukov@google.com \
--cc=fengguang.wu@intel.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mmarek@suse.com \
--cc=pageexec@freemail.hu \
--cc=spender@grsecurity.net \
--cc=yamada.masahiro@socionext.com \
/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.