From: Michal Simek <monstr@monstr.eu>
To: "Steven J. Magnani" <steve@digidescorp.com>
Cc: microblaze-uclinux@itee.uq.edu.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] microblaze: Fix ftrace_update_ftrace_func panic
Date: Mon, 05 Apr 2010 16:26:17 +0200 [thread overview]
Message-ID: <4BB9F309.8070807@monstr.eu> (raw)
In-Reply-To: <1270232979-12113-1-git-send-email-steve@digidescorp.com>
Steven J. Magnani wrote:
> The Microblaze dynamic ftrace code assumes a call ordering that is not met
> in all scenarios. Specifically, executing a command similar to:
>
> echo 105 > /sys/kernel/debug/tracing/set_ftrace_pid
>
> before any other tracing-related commands results in a kernel panic:
>
> BUG: failure at arch/microblaze/kernel/ftrace.c:198/ftrace_update_ftrace_func()!
>
> Recoding ftrace_update_ftrace_func() to use &ftrace_caller directly eliminates
> the need to capture its address elsewhere (and thus rely on a particular call
> sequence).
I would like to replicate this problem to see that there is. I am not
able to reach this fault
Please copy & paste log with your commands.
Thanks,
Michal
>
> Signed-off-by: Steven J. Magnani <steve@digidescorp.com>
> ---
> diff -uprN a/arch/microblaze/kernel/ftrace.c b/arch/microblaze/kernel/ftrace.c
> --- a/arch/microblaze/kernel/ftrace.c 2010-04-02 13:10:54.000000000 -0500
> +++ b/arch/microblaze/kernel/ftrace.c 2010-04-02 13:13:29.000000000 -0500
> @@ -151,13 +151,10 @@ int ftrace_make_nop(struct module *mod,
> return ret;
> }
>
> -static int ret_addr; /* initialized as 0 by default */
> -
> /* I believe that first is called ftrace_make_nop before this function */
> int ftrace_make_call(struct dyn_ftrace *rec, unsigned long addr)
> {
> int ret;
> - ret_addr = addr; /* saving where the barrier jump is */
> pr_debug("%s: addr:0x%x, rec->ip: 0x%x, imm:0x%x\n",
> __func__, (unsigned int)addr, (unsigned int)rec->ip, imm);
> ret = ftrace_modify_code(rec->ip, imm);
> @@ -194,12 +191,9 @@ int ftrace_update_ftrace_func(ftrace_fun
> ret = ftrace_modify_code(ip, upper);
> ret += ftrace_modify_code(ip + 4, lower);
>
> - /* We just need to remove the rtsd r15, 8 by NOP */
> - BUG_ON(!ret_addr);
> - if (ret_addr)
> - ret += ftrace_modify_code(ret_addr, MICROBLAZE_NOP);
> - else
> - ret = 1; /* fault */
> + /* We just need to replace the rtsd r15, 8 with NOP */
> + ret += ftrace_modify_code((unsigned long)&ftrace_caller,
> + MICROBLAZE_NOP);
>
> /* All changes are done - lets do caches consistent */
> flush_icache();
>
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2010-04-05 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 18:29 [PATCH] microblaze: Fix ftrace_update_ftrace_func panic Steven J. Magnani
2010-04-05 14:26 ` Michal Simek [this message]
2010-04-05 18:04 ` Steven J. Magnani
2010-04-06 6:29 ` Michal Simek
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=4BB9F309.8070807@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=steve@digidescorp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.