All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: 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: Tue, 06 Apr 2010 08:29:16 +0200	[thread overview]
Message-ID: <4BBAD4BC.3000300@monstr.eu> (raw)
In-Reply-To: <1270490674.3042.174.camel@iscandar.digidescorp.com>

Steven J. Magnani wrote:
> On Mon, 2010-04-05 at 16:26 +0200, Michal Simek wrote:
>> 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.
> 

> # echo 80 > /sys/kernel/debug/tracing/set_ftrace_pid
> BUG: failure at
> arch/microblaze/kernel/ftrace.c:202/ftrace_update_ftrace_func()!
> Kernel panic - not syncing: BUG!

I am able to replicate this fault on both versions.
Added to next branch.

Thanks,
Michal


-- 
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

      reply	other threads:[~2010-04-06  6:29 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
2010-04-05 18:04   ` Steven J. Magnani
2010-04-06  6:29     ` Michal Simek [this message]

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=4BBAD4BC.3000300@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.