public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: fche@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-332-gf2b610b Date: Sat, 27 Nov 2010 23:54:00 -0000 [thread overview] Message-ID: <20101127235423.6598.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 f2b610b6295628ae1fef744421c293883f1e4298 (commit) from d1bf48fa8dcb9157337d2c651f018fbb0c45f7f7 (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 f2b610b6295628ae1fef744421c293883f1e4298 Author: Frank Ch. Eigler <fche@elastic.org> Date: Sat Nov 27 18:48:52 2010 -0500 PR10651 / RHBZ653286: mod_timer vs. del_timer_sync races It appears possible for del_timer_sync (from outside) and mod_timer (from within a timer callback) to race. Defeat this race by ensuring that the timer callback checks an atomic_t flag before rescheduling itself with mod_timer. * runtime/transport/relay_v2.c (transport_state): Turn into an atomic_t. Update users. (__stp_relay_wakeup_timer): Observe flag. (_stp_transport_data_fs_{start,stop}): Update flag before timer manipulations. * runtime/transport/ring_buffer.c: Ditto for corresponding functions. ----------------------------------------------------------------------- Summary of changes: runtime/transport/relay_v2.c | 23 +++++++++++++---------- runtime/transport/ring_buffer.c | 28 +++++++++++++++------------- 2 files changed, 28 insertions(+), 23 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-11-27 23: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=20101127235423.6598.qmail@sourceware.org \ --to=fche@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).