This is the mail archive of the systemtap-cvs@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]

[SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-643-ga53e79a


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "systemtap: system-wide probe/trace tool".

The branch, master has been updated
       via  a53e79a9c936a26cbf7757a57e70ced3b147b2b8 (commit)
       via  9100a7df0c25e631720f57a4016761ecb1fee1a3 (commit)
      from  f63e9688766829812c940be66cca331a4371a3ec (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit a53e79a9c936a26cbf7757a57e70ced3b147b2b8
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Wed Dec 21 13:34:05 2011 -0500

    PR13536: eliminate staprun -u uprobes check/load race condition.
    
    (Note that there is no security impact to this change.  The worst that
    could happen before were unnecessary staprun startup errors.)
    
    * runtime/staprun/staprun_funcs.c (insert_module): Return a nontrivial
      error return code in some cases.  (More needed!)  Don't kvetch about
      a failing init_module(2).
    * runtime/staprun/staprun.c (enable_uprobes): Don't grep kallsyms for
      an optimistic early abort.  Just call insert_module.  Don't freak upon
      an EEXIST.
      (insert_stap_module): Kvetch about a failing insert_module().
    
    * testsuite/systemtap.base/buildid.exp: Stop using that profane artefact
      of an obsolete past, "staprun -u".

commit 9100a7df0c25e631720f57a4016761ecb1fee1a3
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Wed Dec 21 13:30:28 2011 -0500

    testsuite: use [uprobes_p] as applicability test
    
    This is necessary as [utrace_p] is becoming trueish for
    tracepoint/taskfinder2 kernels.

-----------------------------------------------------------------------

Summary of changes:
 runtime/staprun/staprun.c                          |   29 ++++++++++---------
 runtime/staprun/staprun_funcs.c                    |    4 +-
 testsuite/systemtap.base/buildid.exp               |   13 +++++---
 testsuite/systemtap.base/cu-decl.exp               |    4 +-
 testsuite/systemtap.base/hash_add_buildid.exp      |    1 +
 .../systemtap.base/unresolved-struct-typedef.exp   |    2 +-
 6 files changed, 29 insertions(+), 24 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


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