From: Peter Oberparleiter <oberpar@linux.ibm.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Riku Voipio <riku.voipio@linaro.org>,
Frantisek Hrbata <fhrbata@redhat.com>,
Masahiro Yamada <yamada.m@jp.panasonic.com>,
linux-kernel@vger.kernel.org, lkp@01.org
Subject: Re: [gcov_module_notifier] WARNING: CPU: 0 PID: 155 at mm/slab_common.c:996 kmalloc_slab+0x1f/0x79
Date: Fri, 20 Apr 2018 13:08:07 +0200 [thread overview]
Message-ID: <4e2d71d1-e945-e2c3-cf8f-e19df52df6f5@linux.ibm.com> (raw)
In-Reply-To: <20180419025854.uasnqkaflr45zeat@wfg-t540p.sh.intel.com>
On 19.04.2018 04:58, Fengguang Wu wrote:
> FYI this happens in mainline kernel 4.17.0-rc1.
> It at least dates back to v4.5 .
This is likely the result of compiling the kernel with GCC 7 while
specifying that gcov-kernel should expect GCC <= 3.4 format data:
dmesg:
> (gcc version 7.3.0 (Debian 7.3.0-1)) #31 Mon Apr 16 23:17:50 CST 2018
.config:
> # CONFIG_GCOV_FORMAT_AUTODETECT is not set
> CONFIG_GCOV_FORMAT_3_4=y
> # CONFIG_GCOV_FORMAT_4_7 is not set
As such, it is an expected test failure. Assuming that this is a
randconfig test, my recommendation would be to blacklist
"CONFIG_GCOV_FORMAT_3_4=y" when using GCC >3.4.
--
Peter Oberparleiter
Linux on Z Development - IBM Germany
next prev parent reply other threads:[~2018-04-20 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 2:58 [gcov_module_notifier] WARNING: CPU: 0 PID: 155 at mm/slab_common.c:996 kmalloc_slab+0x1f/0x79 Fengguang Wu
2018-04-20 11:08 ` Peter Oberparleiter [this message]
2018-04-20 12:38 ` Fengguang Wu
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=4e2d71d1-e945-e2c3-cf8f-e19df52df6f5@linux.ibm.com \
--to=oberpar@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=fengguang.wu@intel.com \
--cc=fhrbata@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=riku.voipio@linaro.org \
--cc=yamada.m@jp.panasonic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox