linux-kernel - Re: backtrace issue in MIPS 3.0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAJ8eaTyJnqkyVN4k_cVZ1SXvwGf_4JYGVWZDwZ_Zjvq34NGvtg@mail.gmail.com>
Date:	Wed, 25 Apr 2012 18:38:28 +0530
From:	naveen yadav <yad.naveen@...il.com>
To:	Ralf Baechle <ralf@...ux-mips.org>, linux-mips@...ux-mips.org,
	linux-kernel@...r.kernel.org
Subject: Re: backtrace issue in MIPS 3.0

Add lkml also

On Wed, Apr 25, 2012 at 6:17 PM, naveen yadav <yad.naveen@...il.com> wrote:
> Dear Ralf,
>
> We observe the following issue in kernel backtrace.
>
> Scenario:1
> Correct backtrace - if HAVE_FUNCTION_TRACER is disable.
>
> ====[ backtrace testing ]===========
> Testing a backtrace from process context.
> The following trace is a kernel self test and not a bug!
> Testing a backtrace.
> The following trace is a kernel self test and not a bug!
> Call Trace:
> [<80295134>] dump_stack+0x8/0x34
> [<c0946060>] backtrace_regression_test+0x60/0x94 [sisc_backtrcae]
> [<800004f0>] do_one_initcall+0xf0/0x1d0
> [<80060954>] sys_init_module+0x19c8/0x1c60
> [<8000a418>] stack_done+0x20/0x40
>
> Scenaro-2:
> if HAVE_FUNCTION_TRACER is enabled
>        HAVE_FUNCTION_TRACER function enables FRAME_POINTER
>      menuconfig->
>               kernel hacking->
>                                    tracers->
>                                                 Kernel Function Tracer
>
> ====[ backtrace testing ]===========
>
> Testing a backtrace from process context.
>
> The following trace is a kernel self test and not a bug!
>
> Testing a backtrace.
>
> The following trace is a kernel self test and not a bug!
>
> Call Trace:
>
> [<802e5164>] dump_stack+0x1c/0x50
>
> [<802e5164>] dump_stack+0x1c/0x50
>
> ====[ end of backtrace testing ]====
>  ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Sample Code:
>
> #include <linux/module.h>
> #include <linux/sched.h>
> #include <linux/delay.h>
> //static struct timer_list backtrace_timer;
>
> static void backtrace_test_timer()
> {
>        printk("Testing a backtrace.\n");
>        printk("The following trace is a kernel self test and not a bug!\n");
>        dump_stack();
> }
> static int backtrace_regression_test(void)
> {
>        printk("====[ backtrace testing ]===========\n");
>        printk("Testing a backtrace from process context.\n");
>        printk("The following trace is a kernel self test and not a bug!\n");
>        backtrace_test_timer();
>        msleep(10);
>        printk("====[ end of backtrace testing ]====\n");
>        return 0;
> }
> static void exitf(void)
> {
> }
>
> module_init(backtrace_regression_test);
> module_exit(exitf);
> MODULE_LICENSE("GPL");
>
>
> objdump is also attached.
>
> Thanks
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/