public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-579-g5876002
Date: Mon, 12 Dec 2011 15:09:00 -0000	[thread overview]
Message-ID: <20111212150955.8666.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  5876002191544908925353c6ea20a0335be7e703 (commit)
       via  262f75989148e759f76f16044677182a218bf680 (commit)
       via  ab86339871ab6e281cbb3c62ea9b1d5f6a53e1f4 (commit)
      from  64e807c2d576126a24ffb251fb4108f3940ece0b (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 5876002191544908925353c6ea20a0335be7e703
Merge: 262f759 64e807c
Author: Mark Wielaard <mjw@redhat.com>
Date:   Mon Dec 12 15:59:28 2011 +0100

    Merge branch 'master' of ssh://sourceware.org/git/systemtap

commit 262f75989148e759f76f16044677182a218bf680
Author: Mark Wielaard <mjw@redhat.com>
Date:   Mon Dec 12 15:54:59 2011 +0100

    Protect just the transport state with _stp_transport_mutex.
    
    _stp_transport_mutex was held over the whole of _stp_handle_start()
    and _stp_cleanup_and_exit(). This is unnecessary and dangerous since
    some functions that get called could sleep. Add a new state variable
    _stp_start_called and protect just that together with _stp_exit_called
    to make sure _stp_handle_start() and _stp_cleanup_and_exit() are only
    executed once.

commit ab86339871ab6e281cbb3c62ea9b1d5f6a53e1f4
Author: Mark Wielaard <mjw@redhat.com>
Date:   Mon Dec 12 13:46:28 2011 +0100

    uprobes.c add rcu_read_lock for pid_task(), rcu_dereference and utrace.
    
    pid_task(), rcu_dereference() and the utrace functions that convert a
    given pid to a task need to be protected by the rcu_read_lock().

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

Summary of changes:
 runtime/transport/transport.c |   50 ++++++++++++++++++++++++++++++----------
 runtime/uprobes2/uprobes.c    |   42 ++++++++++++++++++++++++++++++++--
 2 files changed, 76 insertions(+), 16 deletions(-)


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


                 reply	other threads:[~2011-12-12 15:09 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=20111212150955.8666.qmail@sourceware.org \
    --to=mark@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).