From: Tiejun Chen <tiejun.chen@windriver.com>
To: <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: v2 booke/kprobe: Fix stack corrupt issue when kprobe 'stwu'
Date: Mon, 11 Jul 2011 10:39:36 +0800 [thread overview]
Message-ID: <1310351976-24078-3-git-send-email-tiejun.chen@windriver.com> (raw)
In-Reply-To: <1310351976-24078-2-git-send-email-tiejun.chen@windriver.com>
v1 -> v2: when allocate pgirq_ctx, use 'hw_cpu' to identify cpu ID in exc_lvl_early_init().
BTW, I already validated these patches on fsl mpc8536 by kprobe do_fork() and show_interrupts().
Note this bug I fixed is from another email thread, "[BUG?]3.0-rc4+ftrace+kprobe:
set kprobe at instruction 'stwu' lead to system crash/freeze", Yong Zhang, <yong.zhang0@gmail.com>
previously reported.
Tiejun
next prev parent reply other threads:[~2011-07-11 2:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 2:39 [v2 PATCH 1/2] booke/kprobe: make program exception to use one dedicated exception stack Tiejun Chen
2011-07-11 2:39 ` [v2 PATCH 2/2] booke/kprobe: remove unnecessary preempt_enable_no_resched Tiejun Chen
2011-07-11 2:39 ` Tiejun Chen [this message]
2011-07-11 5:55 ` Ananth N Mavinakayanahalli
2011-07-11 8:34 ` tiejun.chen
2011-07-11 11:28 ` tiejun.chen
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=1310351976-24078-3-git-send-email-tiejun.chen@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).