From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/15219] syscall.exp failures on RHEL5, RHEL6, and rawhide
Date: Tue, 08 Oct 2013 18:03:00 -0000 [thread overview]
Message-ID: <bug-15219-6586-BLTrviym1d@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15219-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15219
--- Comment #10 from David Smith <dsmith at redhat dot com> ---
Created attachment 7226
--> https://sourceware.org/bugzilla/attachment.cgi?id=7226&action=edit
different anti-nested syscall patch
Here's a patch that attempts to fix this problem by avoiding nested syscalls.
It does this by looking at the syscall number. If we're in
syscall.clock_settime, but the syscall number isn't __NR_clock_settime, return.
This is done with macros stored in tapset/linux/syscalls.stpm, called
'__syscall_enter' and '__syscall_enter2'.
With this patch, the syscall test case passes completely on rawhide x86_64
(3.12.0-0.rc2.git0.1.fc21.x86_64).
Note that the patch isn't complete. The nd_syscall tapset files would need to
modified in a similar manner. Also, all nested syscalls weren't avoided, just
the ones needed for syscall.exp to pass.
Also note that the macros could use better names, especially since they also
get called in .return probes.
Comments welcome.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-10-08 18:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 17:54 [Bug tapsets/15219] New: " dsmith at redhat dot com
2013-03-04 17:54 ` [Bug tapsets/15219] " dsmith at redhat dot com
2013-03-04 18:40 ` fche at redhat dot com
2013-06-03 13:38 ` dsmith at redhat dot com
2013-06-04 15:14 ` fche at redhat dot com
2013-06-05 17:58 ` dsmith at redhat dot com
2013-06-06 18:03 ` dsmith at redhat dot com
2013-06-11 14:37 ` dsmith at redhat dot com
2013-06-17 16:10 ` dsmith at redhat dot com
2013-08-26 20:44 ` dsmith at redhat dot com
2013-10-08 18:03 ` dsmith at redhat dot com [this message]
2013-10-08 18:15 ` dsmith at redhat dot com
2013-10-31 17:24 ` dsmith at redhat dot com
2014-01-07 22:02 ` dsmith 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-15219-6586-BLTrviym1d@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).