Re: [tip:tracing/urgent] tracing: Fix too large stack usage in do_one_initcall()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2009-08-21 at 11:13 -0700, Linus Torvalds wrote:
> 
> On Fri, 21 Aug 2009, Andrew Morton wrote:
> > 
> > Do we have a max-stack-depth tracer widget btw?
> 
> Enable FTRACE and then STACK_TRACER. Then just do
> 
> 	cat /sys/kernel/debug/tracing/stack_trace
> 
> and you'll get this.

Just a nitpick, but you will want to also add "stacktrace" to the kernel
command line otherwise it is default off. If you forget to do that, you
can also enable it with /proc/sys/kernel/stack_tracer_enabled.

But if you forget what to do, the code will remind you:

[root@mxf ~]# cat /sys/kernel/debug/tracing/stack_trace 
        Depth    Size   Location    (-1 entries)
        -----    ----   --------
#
#  Stack tracer disabled
#
# To enable the stack tracer, either add 'stacktrace' to the
# kernel command line
# or 'echo 1 > /proc/sys/kernel/stack_tracer_enabled'
#


-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Stable Commits]     [Linux Stable Kernel]     [Linux Kernel]     [Linux USB Devel]     [Linux Video &Media]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux