This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/21362] New: more syscall nesting problems
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Fri, 07 Apr 2017 14:58:58 +0000
- Subject: [Bug tapsets/21362] New: more syscall nesting problems
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=21362
Bug ID: 21362
Summary: more syscall nesting problems
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
Target Milestone: ---
After filing bug #21353, I wondered if the syscall testsuite couldn't find
syscall nesting issues. The systemtap test script uses indentation to show
nesting:
msg_queue: msgctl (2523136, IPC_64|IPC_RMID, 0x0) =
msg_queue: msgctl (2523136, IPC_64|IPC_RMID, 0x0) = 0
But, the test script looking at that output didn't care that syscall nesting
was going on. With that changed, I'm seeing several failures. On RHEL7 x86_64,
I'm seeing failures in the following tests: lseek, msg_queue, semop, uid, and
uid16.
These failures should be investigated and fixed. I'm sure the list of failing
tests will be architecture dependent.
--
You are receiving this mail because:
You are the assignee for the bug.