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-551-g8bb4f64
Date: Tue, 06 Dec 2011 21:35:00 -0000	[thread overview]
Message-ID: <20111206213531.5957.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  8bb4f643d872744925423b845c5319cb9ec97be6 (commit)
      from  f6844d79b59dfcc5a33e3c48d7a99311a8f9247a (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 8bb4f643d872744925423b845c5319cb9ec97be6
Author: Dave Brolley <brolley@redhat.com>
Date:   Tue Dec 6 16:32:26 2011 -0500

    staprun: User privilege checking in restricted environments.
    
    - Make sure staprun builds with all combinations of HAVE_ELF and
      HAVE_ELF_GETSHDRSTRNDX.
    - When HAVE_ELF_GETSHDRSTRNDX is not defined, we must assume the
      highest required privilege level for signed modules (stapsys).

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

Summary of changes:
 privilege.h                     |    3 ++-
 runtime/staprun/staprun_funcs.c |   31 +++++++++++++++++--------------
 2 files changed, 19 insertions(+), 15 deletions(-)


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


                 reply	other threads:[~2011-12-06 21:35 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=20111206213531.5957.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).