From: Josh Stone <jistone@redhat.com>
To: systemtap@sourceware.org
Subject: Re: automated way to find functions that we might want to blacklist
Date: Thu, 19 Jan 2012 16:42:00 -0000 [thread overview]
Message-ID: <4F1847E0.7010103@redhat.com> (raw)
In-Reply-To: <20120119131003.GC26534@sli.dy.fi>
On 01/19/2012 05:10 AM, Sami Liedes wrote:
> Is there a way to blacklist a single place where one of these is
> inlined? I don't think blacklisting the offending function where these
> are inlined would prevent the crash with 'probe
> kernel.function("hash_64") {}'. Or would it?
Currently, we don't. We do check whether the inlined address is
anywhere within a __kprobes-marked function, but the name comparison is
only done on the inline function itself. We could enhance this though,
because that nesting hierarchy is present in DWARF.
prev parent reply other threads:[~2012-01-19 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 23:33 Timo Juhani Lindfors
2011-12-24 14:27 ` Sami Liedes
2012-01-15 21:46 ` Sami Liedes
2012-01-15 22:13 ` Sami Liedes
2012-01-17 20:18 ` David Smith
2012-01-17 21:55 ` Sami Liedes
2012-01-19 13:10 ` Sami Liedes
2012-01-19 16:42 ` Josh Stone [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=4F1847E0.7010103@redhat.com \
--to=jistone@redhat.com \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).