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-695-g73f52eb Date: Mon, 30 Jan 2012 18:51:00 -0000 [thread overview] Message-ID: <20120130185101.28200.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 73f52eb43a66f78c21bd8e61bd25f63415f396f0 (commit) from d680a5e139d81c95862277923124b16094d903cb (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 73f52eb43a66f78c21bd8e61bd25f63415f396f0 Author: Dave Brolley <brolley@redhat.com> Date: Mon Jan 30 13:40:16 2012 -0500 PR 13631 and other rework of multi-privilege level support - PR 13631 - Detection of Reqested Privilege Level in stap-server - Parsing of the client's command now uses getopt_long and shares the getopt input with session.cxx - cmdline.cxx, cmdline.h - Do not allow multiple privilege-setting options to specify different privilege levels. - No longer a need for stap-serverd to generate a --privilege option for the spawned stap. - stap-serverd cannot (and no longer does) rely on knowledge of the highest signed privilege level when evaluating the user's credentials. - Simplified user credentials test against those required by the module in stap-serverd. - Some kernel.* probes were being registered for use by stapdev only. Corrected to be stapdev | stapsys. - Corrected testsuite problem which was hiding this bug. ----------------------------------------------------------------------- Summary of changes: Makefile.am | 4 +- Makefile.in | 44 ++++++- cmdline.cxx | 54 +++++++ cmdline.h | 55 ++++++++ privilege.cxx | 18 --- privilege.h | 10 +- runtime/staprun/staprun_funcs.c | 35 +++--- session.cxx | 147 +++++++------------- session.h | 3 +- stap-serverd.cxx | 102 ++++++++++---- tapsets.cxx | 4 +- .../systemtap.unprivileged/unprivileged_probes.exp | 2 +- translate.cxx | 1 - 13 files changed, 302 insertions(+), 177 deletions(-) create mode 100644 cmdline.cxx create mode 100644 cmdline.h hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-01-30 18:51 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=20120130185101.28200.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).