[Bug translator/11347] New: intra-tapset visibility scoping for embedded-c functions

[fche at redhat dot com]

There are cases where a tapset embedded-c function is known
to be safe from the context of the probe that calls it, but
cannot easily be made safe to call from arbitrary contexts.
It would be desirable for such embedded-c functions to be
only visible (resolvable) to probes/aliases within that tapset.

Since systemtap lacks a formal module system, this would be a
baby step in this direction.  One simple possibility would be
to have a policy/mechanism that treats embedded-c functions
with a "__" prefix as being only visible to elements in the
same tapset file as where they are defined.  (Treating
globals, script functions, and probes as similarly visibility
restricted might not provide any additional safety, but could
be considered for sake of simplicity.)

This would let such semi-vulnerable embedded-c functions be
labeled __something.

(irc:)
mjw would it make sense to have a mechanism to hide file/tapset local functions
mjw so they just cannot be called "out of context"?
* fche was thinking the same thing earlier today
mjw was just reading the nfs tapset patches
mjw and they have lots of __get-foo-bar() thingies
mjw hmm, won't fully work
mjw aux_syscalls.stp is used by multiple other tapsets
fche cut & paste then

-- 
           Summary: intra-tapset visibility scoping for embedded-c functions
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: fche at redhat dot com


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

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.