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-142-gd117a23 Date: Tue, 27 Oct 2009 20:54:00 -0000 [thread overview] Message-ID: <20091027205443.12769.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 d117a23e6883640be751523274811d9d5e9dcc11 (commit) via a1995fef7f86ee6d1c3860cfb7e2652d986e4aa9 (commit) from f70d5f6b702e8da5c6affb3f34836c466b01f1b9 (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 d117a23e6883640be751523274811d9d5e9dcc11 Author: Josh Stone <jistone@redhat.com> Date: Tue Oct 27 13:52:34 2009 -0700 PR10854 cont'd: Add a testcase for the reproducer commit a1995fef7f86ee6d1c3860cfb7e2652d986e4aa9 Author: Josh Stone <jistone@redhat.com> Date: Tue Oct 27 12:15:29 2009 -0700 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 | 38 ++++++++++++++++++++------------- testsuite/systemtap.base/pr10854.exp | 31 +++++++++++++++++++++++++++ testsuite/systemtap.base/pr10854.stp | 20 +++++++++++++++++ 3 files changed, 74 insertions(+), 15 deletions(-) create mode 100644 testsuite/systemtap.base/pr10854.exp create mode 100644 testsuite/systemtap.base/pr10854.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-10-27 20:54 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=20091027205443.12769.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: linkBe 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).