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 37/47] kernel/locking/lockdep.c:2806:2: error: implicit declaration of function 'print_lock_trace'
Date: Mon, 15 Apr 2019 06:26:18 +0800 [thread overview]
Message-ID: <201904150618.0j81rctR%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2500 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/stacktrace
head: 63c35ea6b829a0f98d307a8dec038095681ecd13
commit: 88e5708cae1e9cb0cca97bb0af5866ac54532ceb [37/47] lockdep: Simplify stack trace handling
config: x86_64-randconfig-l2-201915 (attached as .config)
compiler: gcc-5 (Debian 5.5.0-3) 5.4.1 20171010
reproduce:
git checkout 88e5708cae1e9cb0cca97bb0af5866ac54532ceb
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
kernel/locking/lockdep.c: In function 'print_usage_bug':
>> kernel/locking/lockdep.c:2806:2: error: implicit declaration of function 'print_lock_trace' [-Werror=implicit-function-declaration]
print_lock_trace(hlock_class(this)->usage_traces + prev_bit, 1);
^
cc1: some warnings being treated as errors
vim +/print_lock_trace +2806 kernel/locking/lockdep.c
2780
2781 static int
2782 print_usage_bug(struct task_struct *curr, struct held_lock *this,
2783 enum lock_usage_bit prev_bit, enum lock_usage_bit new_bit)
2784 {
2785 if (!debug_locks_off_graph_unlock() || debug_locks_silent)
2786 return 0;
2787
2788 pr_warn("\n");
2789 pr_warn("================================\n");
2790 pr_warn("WARNING: inconsistent lock state\n");
2791 print_kernel_ident();
2792 pr_warn("--------------------------------\n");
2793
2794 pr_warn("inconsistent {%s} -> {%s} usage.\n",
2795 usage_str[prev_bit], usage_str[new_bit]);
2796
2797 pr_warn("%s/%d [HC%u[%lu]:SC%u[%lu]:HE%u:SE%u] takes:\n",
2798 curr->comm, task_pid_nr(curr),
2799 trace_hardirq_context(curr), hardirq_count() >> HARDIRQ_SHIFT,
2800 trace_softirq_context(curr), softirq_count() >> SOFTIRQ_SHIFT,
2801 trace_hardirqs_enabled(curr),
2802 trace_softirqs_enabled(curr));
2803 print_lock(this);
2804
2805 pr_warn("{%s} state was registered at:\n", usage_str[prev_bit]);
> 2806 print_lock_trace(hlock_class(this)->usage_traces + prev_bit, 1);
2807
2808 print_irqtrace_events(curr);
2809 pr_warn("\nother info that might help us debug this:\n");
2810 print_usage_bug_scenario(this);
2811
2812 lockdep_print_held_locks(curr);
2813
2814 pr_warn("\nstack backtrace:\n");
2815 dump_stack();
2816
2817 return 0;
2818 }
2819
---
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: 33980 bytes --]
reply other threads:[~2019-04-14 22:26 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=201904150618.0j81rctR%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®