From: Abhishek Sagar <sagar.abhishek@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] ftrace: prevent ftrace modifications while being kprobe'd
Date: Sat, 21 Jun 2008 23:47:15 +0530 [thread overview]
Message-ID: <485D45AB.3000405@gmail.com> (raw)
Hi Steven/Ingo,
These patches address the problem of kprobe registration interfering with
dynamic ftrace. A kprobe registered on an mcount call-site can modify that
address multiple times during its duration of probing. At the same time,
ftrace may simultaneously modify these locations. This could be fatal
especially if ftrace modifies the call-site during a kprobe registration
on it (between arch_prepare_kprobe and arch_arm_kprobe in __register_kprobe
to be more precise). So as a "fix", I've disabled any updates on the mcount
call-site while it's being kprobe'd.
--
Regards,
Abhishek Sagar
next reply other threads:[~2008-06-21 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 18:17 Abhishek Sagar [this message]
2008-06-23 20:15 ` [PATCH 0/4] ftrace: prevent ftrace modifications while being kprobe'd Ingo Molnar
2008-06-24 3:29 ` Abhishek Sagar
2008-06-26 12:33 ` Ingo Molnar
2008-06-26 17:21 ` Abhishek Sagar
2008-07-03 12:49 ` Ingo Molnar
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=485D45AB.3000405@gmail.com \
--to=sagar.abhishek@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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