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 34/47] drivers/gpu/drm/drm_mm.c:136:3: error: implicit declaration of function 'stack_trace_snprintf'
Date: Mon, 15 Apr 2019 09:20:09 +0800 [thread overview]
Message-ID: <201904150908.YUUaTBdW%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace
head: 63c35ea6b829a0f98d307a8dec038095681ecd13
commit: 6476291d5b823a05b9c903a65a5f6e6026a02606 [34/47] drm: Simplify stacktrace handling
config: i386-randconfig-a1-201915 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
git checkout 6476291d5b823a05b9c903a65a5f6e6026a02606
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/gpu/drm/drm_mm.c: In function 'show_leaks':
>> drivers/gpu/drm/drm_mm.c:136:3: error: implicit declaration of function 'stack_trace_snprintf' [-Werror=implicit-function-declaration]
stack_trace_snprintf(buf, BUFSZ, entries, nr_entries, 0);
^
cc1: some warnings being treated as errors
vim +/stack_trace_snprintf +136 drivers/gpu/drm/drm_mm.c
116
117 static void show_leaks(struct drm_mm *mm)
118 {
119 struct drm_mm_node *node;
120 unsigned long *entries;
121 unsigned int nr_entries;
122 char *buf;
123
124 buf = kmalloc(BUFSZ, GFP_KERNEL);
125 if (!buf)
126 return;
127
128 list_for_each_entry(node, drm_mm_nodes(mm), node_list) {
129 if (!node->stack) {
130 DRM_ERROR("node [%08llx + %08llx]: unknown owner\n",
131 node->start, node->size);
132 continue;
133 }
134
135 nr_entries = stack_depot_fetch(node->stack, &entries);
> 136 stack_trace_snprintf(buf, BUFSZ, entries, nr_entries, 0);
137 DRM_ERROR("node [%08llx + %08llx]: inserted at\n%s",
138 node->start, node->size, buf);
139 }
140
141 kfree(buf);
142 }
143
---
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: 31693 bytes --]
reply other threads:[~2019-04-15 1:20 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=201904150908.YUUaTBdW%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
all inboxes | Powered by JetHome®