Bug 17178 - syscall/nd_syscall test failures on f20
Summary: syscall/nd_syscall test failures on f20
Status: RESOLVED FIXED
Alias: None
Product: systemtap
Classification: Unclassified
Component: tapsets (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-18 16:56 UTC by David Smith
Modified: 2014-07-22 20:56 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Smith 2014-07-18 16:56:18 UTC 
On f20 (3.15.4-200.fc20.x86_64), the following are new syscall/nd_syscall testsuite failures:

FAIL: 32-bit getsockopt nd_syscall
FAIL: 32-bit setsockopt nd_syscall
FAIL: 32-bit getsockopt syscall
FAIL: 32-bit select syscall
FAIL: 32-bit setsockopt syscall

From some debugging, the getsockopt() failures are happenning because getsockopt() has been moved under socketcall().
Comment 1 David Smith 2014-07-22 20:56:35 UTC 
Fixed in commit 4c49c0b.