From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Timo Juhani Lindfors <timo.lindfors@iki.fi>
Cc: ananth@in.ibm.com, linux-kernel@vger.kernel.org,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S. Miller" <davem@davemloft.net>,
"yrl.pp-manager.tt@hitachi.com" <yrl.pp-manager.tt@hitachi.com>
Subject: Re: Re: Re: kprobing "hash_64.constprop.26" crashes the system, recursion through get_kprobe?
Date: Fri, 01 Mar 2013 20:02:21 +0900 [thread overview]
Message-ID: <51308ABD.2020509@hitachi.com> (raw)
In-Reply-To: <513088E0.4090704@hitachi.com>
(2013/03/01 19:54), Masami Hiramatsu wrote:
> Actually, __kprobes is used much more than we need, because that
> is safer (and also, that is used just for marking functions
> related to kprobes).
>
> Only what functions we need to mark __kprobes is the functions
> called from do_int3, and optimized_callback, until processing
> recursive call (which is done by kprobe_running() and
> reenter_kprobe()).
Ah, I forgot to mention that interrupt/exception/NMI related code too...
Thanks,
--
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
prev parent reply other threads:[~2013-03-01 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 9:42 kprobing "hash_64.constprop.26" crashes the system, recursion through get_kprobe? Timo Juhani Lindfors
2013-03-01 5:31 ` Ananth N Mavinakayanahalli
2013-03-01 5:51 ` Masami Hiramatsu
2013-03-01 8:43 ` Timo Juhani Lindfors
2013-03-01 10:54 ` Masami Hiramatsu
2013-03-01 11:02 ` Masami Hiramatsu [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=51308ABD.2020509@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=timo.lindfors@iki.fi \
--cc=yrl.pp-manager.tt@hitachi.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.