public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: fche@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-643-ga53e79a Date: Wed, 21 Dec 2011 18:40:00 -0000 [thread overview] Message-ID: <20111221184036.3811.qmail@sourceware.org> (raw) 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
reply other threads:[~2011-12-21 18:40 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111221184036.3811.qmail@sourceware.org \ --to=fche@sourceware.org \ --cc=systemtap-cvs@sourceware.org \ --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: linkBe 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).