public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/13868] New: Use UTRACE_ATTACH_ATOMIC when calling utrace create under lock.
Date: Mon, 19 Mar 2012 19:28:00 -0000	[thread overview]
Message-ID: <bug-13868-6586@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=13868

             Bug #: 13868
           Summary: Use UTRACE_ATTACH_ATOMIC when calling utrace create
                    under lock.
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap@sourceware.org
        ReportedBy: mjw@redhat.com
    Classification: Unclassified


commit e46635d5571a655868c2fd57e186fb6edbe77d78
Author: Mark Wielaard <mjw@redhat.com>
Date:   Tue Jan 31 23:06:30 2012 +0100

    Use UTRACE_ATTACH_ATOMIC when calling utrace create under lock.

    UTRACE_ATTACH_ATOMIC is very new, but we need it when calling
    utrace create while holding a lock or in interrupt context.
    If it doesn't exist we do as before (define it as zero).

    See http://sourceware.org/ml/systemtap/2011-q4/msg00340.html

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2012-03-19 19:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 19:28 mjw at redhat dot com [this message]
2012-03-19 19:30 ` [Bug runtime/13868] " fche at redhat dot com
2012-03-19 19:44 ` fche at redhat dot com

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=bug-13868-6586@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@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).