From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/15866] on rawhide, the 'signal.pending' and 'signal.pending.return' probe aliases are broken
Date: Tue, 20 Aug 2013 20:00:00 -0000 [thread overview]
Message-ID: <bug-15866-6586-uzvkwJ5b1M@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15866-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15866
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from David Smith <dsmith at redhat dot com> ---
Fixed in commit fd36a36. On that rawhide kernel, do_sigpending() only has 2
callers, sys_rt_sigpending() and compat_sys_rt_sigpending(). So, the probe
aliases now fall back to using those functions.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2013-08-20 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 19:54 [Bug tapsets/15866] New: " dsmith at redhat dot com
2013-08-20 20:00 ` dsmith at redhat dot com [this message]
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-15866-6586-uzvkwJ5b1M@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).