Bug 1101422

Summary: s390x WARNING: unhandled syscall: 326 (dup3)
Product: Red Hat Enterprise Linux 6 Reporter: Miloš Prchlík <mprchlik>
Component: valgrindAssignee: Mark Wielaard <mjw>
Status: CLOSED ERRATA QA Contact: Miloš Prchlík <mprchlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.6CC: jakub, mfranc
Target Milestone: rc   
Target Release: ---   
Hardware: s390x   
OS: Unspecified   
Whiteboard:
Fixed In Version: valgrind-3.8.1-3.5.el6 Doc Type: Bug Fix
Doc Text:
Cause: Valgrind didn't support the dup3 system calls on powerpc kernels. Consequence: Programs using that system call on powerpc when running under valgrind would get warnings and errors. Fix: valgrind now recognizes the dup3 system calls and handles it properly. Result: Programs running under valgrind on ppc that use the dup3 system call run without warnings or errors.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-14 06:37:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Miloš Prchlík 2014-05-27 07:18:47 UTC
Description of problem:

dup3 function causes valgrind to warn - see https://bugzilla.redhat.com/show_bug.cgi?id=1067486

[0 root@auto-s390-001 ~]# rpm -q valgrind
valgrind-3.8.1-3.4.el6.s390x
[0 root@auto-s390-001 ~]# cat dup3.c
#include <unistd.h>

int main(int argc, char **argv)
{
  dup3(0, 0, 0);

  return 0;
}

[0 root@auto-s390-001 ~]# gcc -o dup3 dup3.c
[0 root@auto-s390-001 ~]# valgrind ./dup3
==52619== Memcheck, a memory error detector
==52619== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==52619== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==52619== Command: ./dup3
==52619== 
--52619-- WARNING: unhandled syscall: 326
--52619-- You may be able to write your own handler.
--52619-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--52619-- Nevertheless we consider this a bug.  Please report
--52619-- it at http://valgrind.org/support/bug_reports.html.
==52619== 
==52619== HEAP SUMMARY:
==52619==     in use at exit: 0 bytes in 0 blocks
==52619==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==52619== 
==52619== All heap blocks were freed -- no leaks are possible
==52619== 
==52619== For counts of detected and suppressed errors, rerun with: -v
==52619== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)
[0 root@auto-s390-001 ~]# 

Version-Release number of selected component (if applicable):

valgrind-3.8.1-3.4.el6.s390x


How reproducible:

Always on s390x, other arches are fine.


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Mark Wielaard 2014-05-27 07:49:16 UTC
This is RHEL7 bug #1067486 and upstream KDE#331337.
Should be trivial to backport.

Comment 4 Miloš Prchlík 2014-06-03 12:26:29 UTC
Verified for build valgrind-3.8.1-3.5.el6.

Comment 5 errata-xmlrpc 2014-10-14 06:37:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1464.html