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.0-134-g991bd3b
Date: Thu, 22 Oct 2009 02:35:00 -0000	[thread overview]
Message-ID: <20091022023459.19169.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  991bd3ba708b467a6b1de0788e0e1e558a087b0d (commit)
      from  29bb0bbc8603edb20de09e79fd8addb4a174947d (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 991bd3ba708b467a6b1de0788e0e1e558a087b0d
Author: Josh Stone <jistone@redhat.com>
Date:   Wed Oct 21 19:27:17 2009 -0700

    Correct the safety-net escape WRT locking
    
    Within a probe body, the "out" label starts the normal exit path,
    including unlocking whatever globals are used in that probe.  Since the
    unprivileged safety-net checks are before the locks are ever grabbed, we
    should bypass the unlock on the way out.
    
    * elaborate.cxx (derived_probe::emit_process_owner_assertion): Use
      "return" instead of "goto out".

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

Summary of changes:
 elaborate.cxx |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)


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


                 reply	other threads:[~2009-10-22  2: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=20091022023459.19169.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: 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).