From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12419 invoked by alias); 9 Feb 2015 17:55:00 -0000 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org Received: (qmail 12269 invoked by uid 48); 9 Feb 2015 17:54:56 -0000 From: "dsmith at redhat dot com" To: systemtap@sourceware.org Subject: [Bug tapsets/17928] A number of the systemtap.syscall/syscall.exp tests fail on 32-bit arm because size_t sign extended to 64-bit value Date: Mon, 09 Feb 2015 17:55:00 -0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: tapsets X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dsmith at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-q1/txt/msg00119.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D17928 --- Comment #9 from David Smith --- (In reply to William Cohen from comment #3) > The changes helped quite a bit. Before the patches: >=20 > testcase ./systemtap.syscall/syscall.exp completed in 211 seconds >=20 > =3D=3D=3D systemtap Summary =3D=3D=3D >=20 > # of expected passes 85 > # of unexpected failures 28 > # of untested testcases 2 > # of unsupported tests 4 >=20 >=20 > After the patches the test results are significantly improved: >=20 > testcase ./systemtap.syscall/syscall.exp completed in 217 seconds >=20 > =3D=3D=3D systemtap Summary =3D=3D=3D >=20 > # of expected passes 101 > # of unexpected failures 13 > # of untested testcases 1 > # of unsupported tests 6 > runtest completed at Fri Feb 6 16:23:55 2015 >=20 > Comparing the systemtap.sum files there all the no new failures. The > following tests remain as failure: >=20 > FAIL: 32-bit alarm syscall (can't set timer to time in past)=20 > FAIL: 32-bit chmod syscall (chmod arg2 of -1 get odd 01777777777777777777= 777) > FAIL: 32-bit dup syscall (not getting correct args for dup3) > FAIL: 32-bit fadvise64 syscall (test crashs on first fadvise64) > FAIL: 32-bit keyctl syscall (returns -EACCES for keyctl syscall) > FAIL: 32-bit mmap syscall (mlock arg2 !=3D 4096) > FAIL: 32-bit poll syscall (epoll_wait not mapped to epoll_pwait) > FAIL: 32-bit recv syscall (doesn't match one recv) > FAIL: 32-bit recvfrom syscall (recvfrom mishandle 32-bit arg (-1)) > FAIL: 32-bit send syscall (looks similar to recv syscall for send) > FAIL: 32-bit sendmsg syscall(looks similar to recv syscall for sendmsg) > FAIL: 32-bit shmat syscall (returning -EINVAL for several shmat/ > FAIL: 32-bit uid syscall (gets wrong value for setuid) >=20 > Will attach the systemtap.log in a moment for details. I looked through systemtap.log, and have attached a patch that should fix t= he following failures: keyctl, recv, recvfrom, send, and sendmsg All but recvfrom are testcase tweaks. On a 32-bit kernel, MAXSTRINGLEN is o= nly 256, which causes us problems in places. Besides the ones getting arguments incorrectly, the fadvise64 test crash is odd. You might try compiling and running the testcase by hand as root and s= ee if it crashes. --=20 You are receiving this mail because: You are the assignee for the bug.