public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: dsmith@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, rhel54, updated. release-0.9.7-13-g23aa036
Date: Fri, 11 Dec 2009 17:28:00 -0000	[thread overview]
Message-ID: <20091211172826.18150.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, rhel54 has been updated
       via  23aa0369382f6589521ae66a84a9a1b5cc119823 (commit)
      from  9999ccbfe3c944256d3fab3cc82d18dba2cd30fb (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 23aa0369382f6589521ae66a84a9a1b5cc119823
Author: David Smith <dsmith@redhat.com>
Date:   Fri Dec 11 11:27:12 2009 -0600

    PR10854: Use a mutex around transport startup/shutdown
    
    We had a race where the probe setup could be called during/after the
    probe shutdown in abnormal circumstances, which leads to kernel
    callbacks still registered after module unload.  (BOOM)
    
    Now the setup/shutdown activities and related flags are guarded by a
    mutex, so we should have strict ordering.
    
    * runtime/transport/transport.c (_stp_transport_mutex): New.
      (_stp_handle_start): Grab the mutex, and make sure we're not exiting.
      (_stp_cleanup_and_exit): Grab the mutex.
      (_stp_lock_inode, _stp_unlock_inode): Use kernel version for checking
      inode locking type.

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

Summary of changes:
 runtime/transport/transport.c |   41 +++++++++++++++++++++++++----------------
 1 files changed, 25 insertions(+), 16 deletions(-)


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


                 reply	other threads:[~2009-12-11 17:28 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=20091211172826.18150.qmail@sourceware.org \
    --to=dsmith@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).