public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
* [Bug tapsets/21362] more syscall nesting problems
  2017-04-07 14:59 [Bug tapsets/21362] New: more syscall nesting problems dsmith at redhat dot com
@ 2017-04-07 14:59 ` dsmith at redhat dot com
  0 siblings, 0 replies; 2+ messages in thread
From: dsmith at redhat dot com @ 2017-04-07 14:59 UTC (permalink / raw)
  To: systemtap

https://sourceware.org/bugzilla/show_bug.cgi?id=21362

David Smith <dsmith at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|systemtap at sourceware dot org    |dsmith at redhat dot com

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug tapsets/21362] New: more syscall nesting problems
@ 2017-04-07 14:59 dsmith at redhat dot com
  2017-04-07 14:59 ` [Bug tapsets/21362] " dsmith at redhat dot com
  0 siblings, 1 reply; 2+ messages in thread
From: dsmith at redhat dot com @ 2017-04-07 14:59 UTC (permalink / raw)
  To: systemtap

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-04-07 14:59 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-04-07 14:59 [Bug tapsets/21362] New: more syscall nesting problems dsmith at redhat dot com
2017-04-07 14:59 ` [Bug tapsets/21362] " dsmith at redhat dot com

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).