This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug runtime/12890] New: staprun on-the-fly module renaming


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

           Summary: staprun on-the-fly module renaming
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap@sourceware.org
        ReportedBy: fche@redhat.com


Until not too long ago, modprobe used to have an -o NAME option
to change the .ko's .gnu.linkonce.this_module struct's copy
of the module name, in order to permit the same .ko to be
loaded more than once.

This can sometimes be helpful for stap users, should the same
script be desirably used multiply concurrently, and the module
cache/hash were to collide.

The modprobe rename facility was removed by commit 30df3f6e68487
in
git://git.kernel.org/pub/scm/utils/kernel/module-init-tools/module-init-tools.git
for reasons that don't affect systemtap (we don't use module dependencies),
so staprun could conceivably transclude this capability, after signature
checking, and generate a locally unique module name.  It could do this by
default every time too.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]