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-215-g10f1823 Date: Wed, 14 Sep 2011 22:56:00 -0000 [thread overview] Message-ID: <20110914225622.13384.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 10f182319278db84525e93fd04d14db5ad69b9d0 (commit) via 2c9caccb8852f29c32f5daa792277bda7d9b27f8 (commit) via f4b68202c55202857ce11ef41aace7d1c8b1cd12 (commit) from ba354d3072f0df3f1581b0fba8aa7d92a16e0362 (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 10f182319278db84525e93fd04d14db5ad69b9d0 Author: Frank Ch. Eigler <fche@redhat.com> Date: Wed Sep 14 18:49:51 2011 -0400 PR6503: verify build-ids of dynamically arriving modules With the horrible module_sect_attr* hack, the .note.gnu.build-id data may now be verified. * runtime/sym.c (_stp_kmodule_check): New function. * runtime/transport/symbols.c (_stp_module_notifier): Upon MODULE_STATE_COMING, verify build-ids. Reject the module from further consideration upon a mismatch. commit 2c9caccb8852f29c32f5daa792277bda7d9b27f8 Author: Frank Ch. Eigler <fche@redhat.com> Date: Wed Sep 14 17:52:44 2011 -0400 PR6503: get at dynamic module section addresses via horrible hack (tm) Since <linux/module.h> does not declare structs module_sect_attr[s], let's declare it ourselves. We need to get at these, because otherwise there is no way to get at the build-id section address. * runtime/autoconf-module-sect-attrs.c: New (partial) autoconf file. * buildrun.cxx (compile_pass): Build it. * runtime/transport/symbols.c (_stp_module_notifier): Use our own modern (2.6.19+) declaration of these structs to pass all section names/addresses to _stp_kmodule_update_address. commit f4b68202c55202857ce11ef41aace7d1c8b1cd12 Author: Frank Ch. Eigler <fche@redhat.com> Date: Wed Sep 14 17:51:27 2011 -0400 PR6503: note special build-id relocation with -DDEBUG_SYMBOLS * runtime/sym.c (_stp_kmodule_update_address): Specially note .note.gnu.build-id pseudo-section being relocated. ----------------------------------------------------------------------- Summary of changes: buildrun.cxx | 1 + runtime/autoconf-module-sect-attrs.c | 7 +++ runtime/sym.c | 47 ++++++++++++++++++++- runtime/transport/symbols.c | 76 +++++++++++++++++++++++----------- 4 files changed, 105 insertions(+), 26 deletions(-) create mode 100644 runtime/autoconf-module-sect-attrs.c hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-09-14 22:56 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=20110914225622.13384.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).