public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: brolley@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-393-g6e9be5b Date: Tue, 08 Nov 2011 15:29:00 -0000 [thread overview] Message-ID: <20111108152918.4253.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 6e9be5bd74d75dd5ec2c51ad1a783f4ac418cad1 (commit) from 8f7e7a1486f45cd373ecf7dd6ef0b052622496de (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 6e9be5bd74d75dd5ec2c51ad1a783f4ac418cad1 Author: Dave Brolley <brolley@redhat.com> Date: Tue Nov 8 10:15:27 2011 -0500 PR 13128: Backward compatibility for stapusr and stapdev level modules. If no privilege credentials are passed to the module, we can assume that the module was loaded directly by a root level user (insmod) or by an older version of staprun (less than 1.7). In the latter case, if the module requires stapusr or stapdev credentials, we can assume that staprun did the right thing and that the module is safe to run. Otherwise, the required privilege level is unknown to the old staprun and we must abort. ----------------------------------------------------------------------- Summary of changes: translate.cxx | 21 +++++++++++++++------ 1 files changed, 15 insertions(+), 6 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-11-08 15:29 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=20111108152918.4253.qmail@sourceware.org \ --to=brolley@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).