From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Detecting kprobes generated code addresses
Date: Thu, 22 Dec 2016 00:40:50 -0600 [thread overview]
Message-ID: <20161222064050.nxt4baiknnovwmjb@treble> (raw)
Hi Masami,
I would like to make __kernel_text_address() be able to detect whether
an address belongs to code which was generated by kprobes. As far as I
can tell, that information seems to be in the 'pages' lists of
kprobe_insn_slots and kprobe_optinsn_slots. But they seem to be
protected by mutexes. Do you know if there's a sleep-free way to access
that
protected
--
Josh
next reply other threads:[~2016-12-22 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 6:40 Josh Poimboeuf [this message]
2016-12-22 6:42 Detecting kprobes generated code addresses Josh Poimboeuf
2016-12-25 3:13 ` Masami Hiramatsu
2016-12-25 6:16 ` Masami Hiramatsu
2016-12-26 4:30 ` Masami Hiramatsu
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=20161222064050.nxt4baiknnovwmjb@treble \
--to=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=x86@kernel.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).