public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: jistone@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-327-gd4caed2 Date: Fri, 15 Jun 2012 00:09:00 -0000 [thread overview] Message-ID: <20120615000932.9051.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 d4caed28490b1480b29191c9d4c875a0f41175bd (commit) from fdb3f24278a7afc35b716d22b991efc0896a6479 (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 d4caed28490b1480b29191c9d4c875a0f41175bd Author: Josh Stone <jistone@redhat.com> Date: Thu Jun 14 16:52:28 2012 -0700 PR14244: Assert that the real UID has access to debugfs Some systems are now defaulting debugfs to mode 0700. If the user has no access to debugfs, then they won't be able to communicate with the systemtap module. Thus, this should be a non-starter, before even loading the module at all. This was previously causing staprun to fail after loading the module, when it checked R/W access to the module's .ctl file. But since we also restrict removing modules to those you can control, staprun would not unload the new module either. ----------------------------------------------------------------------- Summary of changes: runtime/staprun/staprun_funcs.c | 16 ++++++++++++++-- 1 files changed, 14 insertions(+), 2 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-06-15 0:09 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=20120615000932.9051.qmail@sourceware.org \ --to=jistone@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).