Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:kernel\stacktrace.c Create Date:2022-07-28 10:37:53
Last Modify:2020-03-12 14:18:49 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:stack_trace_print - Print the entries in the stack trace*@entries: Pointer to storage array*@nr_entries: Number of entries in the storage array*@spaces: Number of leading spaces to print

Proto:void stack_trace_print(const unsigned long *entries, unsigned int nr_entries, int spaces)

Type:void

Parameter:

TypeParameterName
const unsigned long *entries
unsigned intnr_entries
intspaces
28  If WARN_ON(!entries) Then Return
31  When i < nr_entries cycle printk - print a kernel message*@fmt: format string* This is printk(). It can be called from any context. We want it to work.* We try to grab the console_lock. If we succeed, it's easy - we log the* output and call the console drivers
Caller
NameDescribe
backtrace_test_saved
dump_object_infoPrint the kmemleak_object information. This function is used mainly for* debugging special cases when kmemleak operations. It must be called with* the object->lock held.
__dump_page_owner
dump_entry_traceThe access to some variables in this macro is racy. We can't use atomic_t* here because all these variables are exported to debugfs. Some of them even* writeable. This is also the reason why a lock won't help much. But anyway,* the races are no big deal