[Bug translator/13659] New: blacklisted functions vs. '__kprobes' functions

["dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=13659

             Bug #: 13659
           Summary: blacklisted functions vs. '__kprobes' functions
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap@sourceware.org
        ReportedBy: dsmith@redhat.com
    Classification: Unclassified


Problem originally pointed out in an email thread:
<http://sourceware.org/ml/systemtap/2011-q4/msg00402.html>

When a function can't be probed with kprobes, it is marked with '__kprobes' in
the kernel source.  The systemtap translator also has an internal blacklist of
function names that shouldn't be probed.

Unfortunately, the list of blacklisted function names approach doesn't work as
fully as marking a function with '__kprobes':

1) If a function is just blacklisted, a user will still be able to probe
inlines within that function.  A user cannot probe inlines within a function
marked with '__kprobes'.

2) A user could user either of the probe types listed below (or any of their
variants) in a function that is only blacklisted:

  kernel.function(ADDRESS)
  kernel.statement(ADDRESS)

The problem here is that the blacklist is just a list of names, no address
information is calculated.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.