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, pr13539, created. release-1.6-683-gf916107
Date: Thu, 26 Jan 2012 15:16:00 -0000	[thread overview]
Message-ID: <20120126151646.8448.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, pr13539 has been created
        at  f916107c257942a9fe962c0693c54a9869db166e (commit)

- Log -----------------------------------------------------------------
commit f916107c257942a9fe962c0693c54a9869db166e
Author: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Date:   Thu Jan 26 09:56:31 2012 -0500

    PR13539: fight uprobes unregister-vs-exit races
    
    While I still cannot see a reason how uprobe_{free,put}_process can
    race uprobe_report_{exit,exec}, I certainly think somebit of cleanup
    can be done.  However I am dont think we need to do a utask or uproc lookup
    from the table. Especially in case of callbacks.
    
    Mostly similar to what Jim proposed.
    I haven't tested this patch myself and I couldn't reproduce the problem.
    [fche corrected some typos and removed meddlesome printk's]

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


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


                 reply	other threads:[~2012-01-26 15:16 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=20120126151646.8448.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: 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).