| |
Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • ShopThe Open Brand -- Problem Reporting and Interpretations System |
|
Problem Report 1108 Details
Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges
This page provides all information on Problem Report 1108.
Report 1108 Actions
Problem Report Number 1108 Submitter's Classification Test Suite problem State Resolved Resolution Rejected (REJ) Problem Resolution ID REJ.X.0310 Raised 1970-01-01 08:00 Updated 2003-03-13 08:00 Published null Product Standard Internationalised System Calls and Libraries Extended (UNIX 95) Certification Program The Open Brand certification program Test Suite VSU version 4.1.1 Test Identification base/write 26 Problem Summary PG4U.00163 This test may fail if close() does not actually break a connection. Problem Text
write 26 is failing intermittently on our platform (for both VSU4.1.1 and
VSU5.0.2A)
The included journal includes 128 consecutive runs of write 26. There are
3 occurrance of failure becuase the
2nd write unexpectedly succeeded, and the remaining 125 passed because the
2nd write failed correctly with EPIPE.
These intermittent failures are due to a timing dependency in the test
suite, as follows. (Note that the timestamps
in the attached explanation do not correspond to the journal above with
repeated runs of write 26, this was from a seperate
run which PASSed where we gathering debug information.)
Step Client Socket
Server Socket
SYN
1 Connect
---------------------------------------------------------->
SYN + ACK
2
<---------------------------------------------------------
ACK
3
----------------------------------------------------------> ACCEPT
ACK + FIN
4
<--------------------------------------------------------- CLOSE
(FINWAIT1)
ACK
5
-----------------------------------------------------------> FINWAIT2
PUSH
6 1st WRITE()
-----------------------------------------------------------> Reject the
inbound
(19:16:59.392965)
(19:16:59.396089)
RESET
7 (19:16:59.397372)
<------------------------------------------------------------
8 2nd WRITE() failing EPIPE (& getting
SIGPIPE)
(19:16:59:401736)
In this scenario, the second WRITE() is failing EPIPE and getting SIGPIPE
(as expected) since the RESET of step 7 had come after 4407 msecs. So if
the second WRITE() of step 8 came to the TCP/IP stack before the RESET of
step 7, it will get SUCCESSFUL return code as same as the first WRITE()
which explains the intermittent results.Test Output
0|1.10 10:10:49 19990318|User: VSU0 (340) TCC Start, Command Line: tcc -e
CAPI baseMarch18
20|/vsu/VSU4.1.1/vsu/CAPI/tetexec.cfg 1|Config Start
30||TET_VERSION=1.10
30||TET_OUTPUT_CAPTURE=False
30||TET_RESCODES_FILE=tet_code
30||TET_EXEC_IN_PLACE=True
30||VSU_IPPORT_RESERVED_VALUE=1024
30||VSU_MASTER_PTY=/dev/ptyp0088
30||VSU_FILE_SYS=OMVSSPB.VSU4.SPARE.HFS
30||VSU_CHAR_SPECIAL=/dev/tty
30||VSU_FILE_NO_MMAP=/dev/null
30||VSU_STREAM_DEV=NONE
30||VSU_STREAMS_MAX_CONTROL_SIZE=65536
30||VSU_STREAMS_MAX_DATA_SIZE=65536
30||VSU_GR_ENT1=BIN,2,BINU
30||VSU_GR_ENT2=COMMUN,603,OMPTY1,OMPTY2,OMPTY3,OMPTY4,OMPTY5,OMPTY6,OMPTY8
,OMPTY9,OMPTY10,OMJOBCT,OMPTASM,OMATTY,OMGETI,OMGETO,OMSETI,OMSETO,OMERMID,
OMYNAME,OMMK10K,OMGETAT,OMSETAT,OMJOBCN,OMGETPG,OMSETPG,OMTCDRN,OMTCFLH,OMT
CFLW,OMDVTTY,OMTCSND,OMTYS
30||VSU_GR_ENT3=DCEGRP,2,
30||VSU_GR_ENT_COUNT=75
30||VSU_PW_ENT1=ACE,295,521,/u/ace,/bin/sh
30||VSU_PW_ENT2=BINU,2,2,/u/binu,/bin/sh
30||VSU_PW_ENT3=BUCK,264,518,/u/buck,/bin/sh
30||VSU_PW_ENT_COUNT=1005
30||VSU_NOT_INUSE_UID1=341
30||VSU_NOT_INUSE_UID2=342
30||VSU_NOT_INUSE_GID1=3401
30||VSU_NOT_INUSE_GID2=3402
30||VSU_INVALID_GID=-2
30||VSU_INVALID_UID=-2
30||VSU_FMTMSG_CONSOLE=/dev/console
30||VSU_SYSLOG_CONSOLE=/dev/console
30||VSU_SYSLOG_CONSOLE_IS_FILE=0
30||VSU_USER_SYSLOG_FILE=/vsu/vsusyslog
30||VSU_USER_FACILITY_INDICATOR=User
30||VSU_DEBUG_SEVERITY_LEVEL_INDICATOR=Debug
30||VSU_INFO_SEVERITY_LEVEL_INDICATOR=Info
30||VSU_NOTICE_SEVERITY_LEVEL_INDICATOR=Notice
30||VSU_WARNING_SEVERITY_LEVEL_INDICATOR=Warning
30||VSU_ERR_SEVERITY_LEVEL_INDICATOR=Err
30||VSU_CRIT_SEVERITY_LEVEL_INDICATOR=Crit
30||VSU_ALERT_SEVERITY_LEVEL_INDICATOR=Alert
30||VSU_EMERG_SEVERITY_LEVEL_INDICATOR=Emerg
30||VSU_MACHINE_PERFORMANCE=50
30||VSU_DATE_CMD=/bin/date '+%b %e %T'
30||VSU_ACCESS_PG_ACROSS_SESSION=1
30||VSU_CORE_FILE=CEEDUMP*
30||VSU_MAX_MAP_REGIONS_PER_PROC=0
30||VSU_MINIMUM_POLL_GRANULARITY=1
30||VSU_MINIMUM_SELECT_GRANULARITY=1000
30||VSU_MINIMUM_UALARM_GRANULARITY=1
30||VSU_MINIMUM_USLEEP_GRANULARITY=1
30||VSU_PAGE_SIZE=4096
30||VSU_READ_READS_DIRECTORY=1
30||VSU_SET_OG_SYMLINK=1
30||VSU_SETPGRP_CREATES_SESSION=0
30||VSU_SIGNAL_GENERATING_CORE=unsupported
30||VSU_SETPRIORITY_HIGHEST_PRIORITY=-20
30||VSU_SETPRIORITY_LEAST_PRIORITY=19
30||VSU_SUPPORTS_INFINITY=0
30||VSU_TRUNCATE_SBITS_RESET=0
30||VSU_VALLOC_RETURNS_UNIQUE_PTR=0
30||VSU_WRITEV_FIFO_INTERLEAVING=1
30||VSU_WRITEV_PIPE_INTERLEAVING=1
30||VSU_WRITEV_SBITS_RESET=0
30||VSU_SUPPORTS_AF_INET_STREAM=1
30||VSU_SUPPORTS_AF_INET_DGRAM=1
30||VSU_SUPPORTS_AF_INET_SEQPACKET=0
30||VSU_SUPPORTS_AF_UNIX_STREAM=1
30||VSU_SUPPORTS_AF_UNIX_DGRAM=1
30||VSU_SUPPORTS_AF_UNIX_SEQPACKET=0
30||VSU_SUPPORTS_AF_INET=1
30||VSU_SUPPORTS_AF_UNIX=1
30||VSU_SUPPORTS_SOCK_STREAM=1
30||VSU_SUPPORTS_SOCK_DGRAM=1
30||VSU_SUPPORTS_SOCK_SEQPACKET=0
30||VSU_HOST_ADDR=129.40.217.7
30||VSU_HOST_ENTRY=129.40.217.7,J11.POK.IBM.COM,J11
30||VSU_HOST_NAME=J11
30||VSU_HOST_REMOTE_ADDR=129.40.217.7
30||VSU_OTHER_HOST_ADDR=9.117.138.61
30||VSU_OTHER_HOST_NAME=OEAIX8
30||VSU_HOST1_ENTRY=129.40.217.6,OEBRAND.POK.IBM.COM,OEBRAND,J10.POK.IBM.CO
M,J10
30||VSU_HOST2_ENTRY=129.40.217.7,J11.POK.IBM.COM,J11
30||VSU_HOST_CNT=4
30||VSU_NET1_ENTRY=JIMREGION,9
30||VSU_NET2_ENTRY=EASTERN2,9
30||VSU_NET_CNT=4
30||VSU_PROTO1_ENTRY=ip,0,
30||VSU_PROTO2_ENTRY=icmp,1,
30||VSU_PROTO_CNT=4
30||VSU_SERV1_ENTRY=echo,7/tcp
30||VSU_SERV2_ENTRY=echo,7/udp
30||VSU_SERV_CNT=92
30||VSU_ADDRESS_INVALID=1.2.3.4
30||VSU_CONNECT_TIMEOUT=190
30||VSU_AF_INVALID=69
30||VSU_PROTO_FOR_AF_INVALID=1,55
30||VSU_PROTO_INVALID=55
30||VSU_LISTEN_LIMIT=0
30||VSU_XCURSES_LOCALE=xcurses
30||VSU_NO_BASE_COLOR=0
30||VSU_DEBUG_ENTER=0
30||VSU_DEBUG_EXIT=0
30||VSU_DEBUG=1
40||Config End
70||"SPEC1170TESTSUITE SECTION BaseMar18 x x x x "
70||"SPEC1170TESTSUITE AREA write 0"
10|0 /tset/CAPIbase/fwrite/fwrite26 10:10:50|TC Start, scenario ref 121-52
15|0 1.10 1|TCM Start
400|0 26 1 10:10:50|IC Start
200|0 1 10:10:50|TP Start
520|0 1 704643089 1 1|SPEC1170TESTSUITE CASE 26
520|0 1 704643089 1 2|If the implementation supports a communications
domain
520|0 1 704643089 1 3|and a connection-oriented socket type:
520|0 1 704643089 1 4|EPIPE in errno and return -1 on a call to ssize_t
520|0 1 704643089 1 5|write(int fildes, const void *buf, size_t nbyte) when
520|0 1 704643089 1 6|fildes refers to a socket that is connection-oriented
520|0 1 704643089 1 7|and the peer is no longer connected.
520|0 1 33554463 1 1|TEST: AF_INET SOCK_STREAM
520|0 1 33554463 1 2|PREP: Create test sockaddr_in: address = 129.40.217.7,
port = 63937
520|0 1 33554463 2 1|PREP: Wait for server to be ready
520|0 1 33554463 2 2|PREP: Create a socket
520|0 1 33554463 2 3|PREP: Connect socket to address 129.40.217.7, port
63937
520|0 1 33554463 2 4|PREP: Tell server to close connection
520|0 1 33554463 2 5|PREP: Wait for connection to close
520|0 1 33554463 2 6|TEST: Write on closed connection
520|0 1 33554463 2 7|TEST: Return value
520|0 1 33554463 2 8|ERROR: write call succeeded unexpectedly, returned 5
520|0 1 33554463 2 9|CLEANUP: Send SIGTERM to server
520|0 1 620757033 1 1|PREP: Server: create socket
520|0 1 620757033 1 2|PREP: Server: bind address 129.40.217.7, port 63937
to socket
520|0 1 620757033 1 3|PREP: Server: listen on socket
520|0 1 620757033 1 4|PREP: Server: notify client server is ready
520|0 1 620757033 1 5|PREP: Server: accept connection
520|0 1 620757033 1 6|INFO: Server: accepted connection from address
129.40.217.7, port 1260
520|0 1 620757033 1 7|PREP: close_server: wait for client to be ready
520|0 1 620757033 1 8|PREP: close_server: close connection
520|0 1 620757033 1 9|PREP: close_server: tell client connection is closed
520|0 1 620757033 1 10|INFO: Server terminated
220|0 1 1 10:10:54|FAIL
410|0 26 1 10:10:54|IC End
80|0 0 10:10:54|TC End
10|1 /tset/CAPIbase/fwrite/fwrite26 10:10:54|TC Start, scenario ref 121-53
15|1 1.10 1|TCM Start
400|1 26 1 10:10:55|IC Start
200|1 1 10:10:55|TP Start
520|1 1 67108895 1 1|SPEC1170TESTSUITE CASE 26
520|1 1 67108895 1 2|If the implementation supports a communications domain
520|1 1 67108895 1 3|and a connection-oriented socket type:
520|1 1 67108895 1 4|EPIPE in errno and return -1 on a call to ssize_t
520|1 1 67108895 1 5|write(int fildes, const void *buf, size_t nbyte) when
520|1 1 67108895 1 6|fildes refers to a socket that is connection-oriented
520|1 1 67108895 1 7|and the peer is no longer connected.
520|1 1 754974737 1 1|TEST: AF_INET SOCK_STREAM
520|1 1 754974737 1 2|PREP: Create test sockaddr_in: address =
129.40.217.7, port = 63985
520|1 1 754974737 2 1|PREP: Wait for server to be ready
520|1 1 754974737 2 2|PREP: Create a socket
520|1 1 754974737 2 3|PREP: Connect socket to address 129.40.217.7, port
63985
520|1 1 754974737 2 4|PREP: Tell server to close connection
520|1 1 754974737 2 5|PREP: Wait for connection to close
520|1 1 754974737 2 6|TEST: Write on closed connection
520|1 1 754974737 2 7|TEST: Return value
520|1 1 754974737 2 8|TEST: errno value
520|1 1 754974737 2 9|CLEANUP: Close socket, kill server
520|1 1 754974737 2 10|TEST: AF_UNIX SOCK_STREAM
520|1 1 754974737 2 11|PREP: Create test sockaddr_un: path =Review Information
Review Type TSMA Review Start Date null Completed null Status Complete Review Recommendation No Resolution Given Review Response
We recommend a test suite deficiency be granted.
Note: We feel this is actually a specification problem and we recommend
the XNET group consider the issue, specifically ammending the spec
to clarify whether close() must actually end a connection before
returning or the disconnect process is allowed to occur asynchronously.
Apparently in practice its actually triggered by the next write rather than
the close() call which is not something the spec allows, though it
probably should.
Note: VSU4.1.1 is no longer valid for branding and thus a TSD cannot
be granted for that release.
Review Type SA Review Start Date null Completed null Status Complete Review Resolution Rejected (REJ) Review Conclusion
This request is refused. A new request needs to be submitted with the
test results from the latest version of VSU5. Please only include one
or two examples of the test which failed. XNET have been approached.
Problem Reporting System Options:
- View Report 1108
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority