Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 2435 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 2435.

Report 2435 Actions

    Problem Report Number 2435
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.1264
    Raised 2005-01-11 05:09
    Updated 2005-01-14 14:26
    Published 2005-01-14 14:26
    Product Standard Internationalised System Calls and Libraries Extended V3 (UNIX 03)
    Certification Program The Open Brand certification program
    Test Suite VSU version 5.2.6
    Test Identification CAPI.os/ioprim/close 11
    Specification Base Definitions Issue 6
    Problem Summary Test assumes no optimization is done in loopback case
    Problem Text The problem with this test assertion is that it assumes no optimization
    is done in the loopback case. For a loopback TCP connection, the
    protocol stack knows exactly the two endpoints. This means that the
    stack can simply put the sent data to the receiver's queue without any
    delay. Conceptually, it is just moving a pointer since the sent data is
    already in the kernel. This eliminates the delay for the sender's
    close. The send is blocked, not because the receiving side isn't
    acking, but to avoid a DoS attack. Because the test assumes that the
    close() will wait, the assertion fails.

    The test case should check to make sure the data has not made it to the
    receiving side of the connection. A small loop to receive and count the
    data after line 368 of close11.c should suffice to show the failure is
    incorrect.
    Test Output 400|0 11 1 12:42:12|IC Start
    200|0 11 12:42:12|TP Start
    520|0 11 00028760 1 1|TEST: AF_INET SOCK_STREAM
    520|0 11 00028760 1 2|PREP: Create test sockaddr_in: address =
    10.1.49.146, port
    = 4989
    520|0 11 00028761 1 1|PREP: Child: wait for parent
    520|0 11 00028761 1 2|PREP: Create a socket
    520|0 11 00028761 1 3|PREP: Connect socket to address 10.1.49.146, port 4989
    520|0 11 00028761 1 4|PREP: Set 5 second linger interval
    520|0 11 00028761 1 5|TEST: Repeatedly send 1024 bytes until send blocks
    520|0 11 00028761 1 6|TEST: close() lingers
    520|0 11 00028761 1 7|ERROR: close() did not linger as per the time
    specified
    520|0 11 00028761 1 8| Expected at least 5 seconds, actually 0 seconds
    520|0 11 00028760 2 1|PREP: Create socket
    520|0 11 00028760 2 2|PREP: Bind to socket
    520|0 11 00028760 2 3|PREP: Call listen for socket
    520|0 11 00028760 2 4|PREP: Signal child parent is ready
    520|0 11 00028760 2 5|PREP: Accept connection
    520|0 11 00028760 2 6|PREP: Wait for child to complete
    220|0 11 1 12:42:14|FAIL
    410|0 11 1 12:42:14|IC End

    Review Information

    Review Type TSMA Review
    Start Date 2005-01-11 05:09
    Last Updated 2005-01-13 01:16
    Completed 2005-01-13 01:16
    Status Complete
    Review Recommendation Test Suite Deficiency (TSD)
    Review Response This is accepted as a fault in the test suite.

    Review Type SA Review
    Start Date 2005-01-13 01:16
    Last Updated 2005-01-13 02:03
    Completed 2005-01-13 02:03
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion This PR represents an agreed test suite deficiency.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority