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-299-g9a1917f
Date: Wed, 12 Oct 2011 14:49:00 -0000	[thread overview]
Message-ID: <20111012144927.30940.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  9a1917ff9ec2165c896437e4bcab61d5c7dfd0fd (commit)
       via  42e38653e141c75c06a320e869a5b3437dc76643 (commit)
      from  832f100d34c6e16222b5a380fbc87270c9cc488e (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 9a1917ff9ec2165c896437e4bcab61d5c7dfd0fd
Author: Dave Brolley <brolley@redhat.com>
Date:   Wed Oct 12 10:41:22 2011 -0400

    PR 13128: Generate section in the module containing privilege level information.
    
    - A list of the groups allowed to load/run the module is generated into the
      section .stap_privilege.

commit 42e38653e141c75c06a320e869a5b3437dc76643
Author: Dave Brolley <brolley@redhat.com>
Date:   Tue Oct 11 14:49:07 2011 -0400

    PR 13128: Modify unprivileged mode infrastructure to support a multi-privilege design
    
    vs the previous boolean privileged/unprivileged design.
    
    - in stap
      - Store the specified privilege level as an enum as opposed to a boolean
      - Test privilege levels against the proper enumerator.
    - in the generated code
      - Generate STP_PRIVILEGE macro with the specified privilege level
      - Generated code tests it against the proper privilege level.

-----------------------------------------------------------------------

Summary of changes:
 csclient.cxx          |    4 +-
 elaborate.cxx         |   16 ++++----
 elaborate.h           |    7 ++--
 hash.cxx              |    2 +-
 runtime/addr-map.c    |    4 +-
 runtime/print.c       |    4 +-
 runtime/runtime.h     |    2 +-
 runtime/task_finder.c |    4 +-
 session.cxx           |   18 +++++-----
 session.h             |    4 ++-
 staptree.cxx          |    4 +-
 tapset-been.cxx       |   18 +++++-----
 tapset-timers.cxx     |   42 +++++++++++-----------
 tapset-utrace.cxx     |   16 ++++----
 tapsets.cxx           |   95 ++++++++++++++++++++++++-------------------------
 translate.cxx         |   21 +++++++++--
 util.cxx              |   29 +++++++++++++++
 util.h                |   17 +++++++++
 18 files changed, 185 insertions(+), 122 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2011-10-12 14:49 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=20111012144927.30940.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: link
Be 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).