Description of problem:

dup3 function causes valgrind to warn:

[root@ibm-z10-70 ~]# cat dup3.c 
#include <unistd.h>

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

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



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

valgrind-3.9.0-4.el7.s390x


How reproducible:

Always on s390x, no warning on x86_64 nor ppc64


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: