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: