From: kbuild test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, tipbuild@zytor.com
Subject: [tip:WIP.core/stacktrace 24/47] mm/slab.c:1490:11: error: 'trace' undeclared; did you mean 'true'?
Date: Mon, 15 Apr 2019 06:05:54 +0800 [thread overview]
Message-ID: <201904150650.Cs6tMaSF%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3067 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace
head: 63c35ea6b829a0f98d307a8dec038095681ecd13
commit: c79cc35c00e9f15a9a32a08569036cb8365c8816 [24/47] mm/slab: Simplify stack trace handling
config: x86_64-randconfig-x003-201915 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout c79cc35c00e9f15a9a32a08569036cb8365c8816
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
mm/slab.c: In function 'store_stackinfo':
>> mm/slab.c:1490:11: error: 'trace' undeclared (first use in this function); did you mean 'true'?
addr += trace.nr_entries;
^~~~~
true
mm/slab.c:1490:11: note: each undeclared identifier is reported only once for each function it appears in
vim +1490 mm/slab.c
^1da177e Linus Torvalds 2005-04-16 1468
^1da177e Linus Torvalds 2005-04-16 1469 #ifdef CONFIG_DEBUG_PAGEALLOC
343e0d7a Pekka Enberg 2006-02-01 1470 static void store_stackinfo(struct kmem_cache *cachep, unsigned long *addr,
^1da177e Linus Torvalds 2005-04-16 1471 unsigned long caller)
^1da177e Linus Torvalds 2005-04-16 1472 {
b8623975 Thomas Gleixner 2019-04-08 1473 int size = cachep->object_size / sizeof(unsigned long);
^1da177e Linus Torvalds 2005-04-16 1474
3dafccf2 Manfred Spraul 2006-02-01 1475 addr = (unsigned long *)&((char *)addr)[obj_offset(cachep)];
^1da177e Linus Torvalds 2005-04-16 1476
b8623975 Thomas Gleixner 2019-04-08 1477 if (size < 5)
^1da177e Linus Torvalds 2005-04-16 1478 return;
^1da177e Linus Torvalds 2005-04-16 1479
^1da177e Linus Torvalds 2005-04-16 1480 *addr++ = 0x12345678;
^1da177e Linus Torvalds 2005-04-16 1481 *addr++ = caller;
^1da177e Linus Torvalds 2005-04-16 1482 *addr++ = smp_processor_id();
b8623975 Thomas Gleixner 2019-04-08 1483 size -= 3;
b8623975 Thomas Gleixner 2019-04-08 1484 #ifdef CONFIG_STACKTRACE
^1da177e Linus Torvalds 2005-04-16 1485 {
c79cc35c Thomas Gleixner 2019-04-14 1486 unsigned int nr_entries;
^1da177e Linus Torvalds 2005-04-16 1487
c79cc35c Thomas Gleixner 2019-04-14 1488 /* Leave one for the end marker below */
c79cc35c Thomas Gleixner 2019-04-14 1489 nr_entries = stack_trace_save(addr, size - 1, 3);
b8623975 Thomas Gleixner 2019-04-08 @1490 addr += trace.nr_entries;
^1da177e Linus Torvalds 2005-04-16 1491 }
b8623975 Thomas Gleixner 2019-04-08 1492 #endif
b8623975 Thomas Gleixner 2019-04-08 1493 *addr = 0x87654321;
^1da177e Linus Torvalds 2005-04-16 1494 }
40b44137 Joonsoo Kim 2016-03-15 1495
:::::: The code at line 1490 was first introduced by commit
:::::: b86239751f8c4d6fc43f6a9eca29e77b0319f5d7 mm/slab: Fix broken stack trace storage
:::::: TO: Thomas Gleixner <tglx@linutronix.de>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29463 bytes --]
reply other threads:[~2019-04-14 22:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201904150650.Cs6tMaSF%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tipbuild@zytor.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