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

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1308 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 1308.

Report 1308 Actions

    Problem Report Number 1308
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0590
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1998-05-28 08:00
    Product Standard Internationalised System Calls and Libraries Extended V2 (UNIX 98)
    Certification Program The Open Brand certification program
    Test Suite VSU version 5.0.2
    Test Identification CAPIbase/ioctl 85
    Problem Summary TSD4U.00228 This test may fail due to implementation restrictions on how much data can be sent to a STREAMS-based pty.
    Problem Text
    The above testcase fails due to the flow control in the underlying
    STREAMS device after writing 7 control buffers of length 50 bytes
    each and 7 data buffers of length 50 bytes each. Due to the flow
    control in the underlying STREAM, only 6 messages can reside at the
    read end of STREAM. This is why the subsequent ioctl call to count
    the number of messages (I_READ) at read end returns 6 and not 7 as
    expected by the test program.

    The X/Open Standard does not specify the flow control values of the
    pseudo-tty interface. The test therefore should not make any
    assumptions about the flow control values. It should instead first
    determine the amount of write that will finally flow control or block
    and then write the appropriate amount of data so that all the data
    written on the slave side makes it over to the master side without
    any flow control. Then the test should issue ioctl with the I_READ
    command on the master side.
    Test Output
    TEST PURPOSE #85
    A successful call to int ioctl(int fildes, I_NREAD,
    int *arg) when fildes refers to a STREAMS device shall
    count the number of data bytes in data blocks in the
    first message on the STREAM head read queue, place
    this value in the location pointed to by arg, and
    return the number of messages on the STREAM head read
    queue.
    PREP: Open master pseudo tty
    PREP: Determine if pseudo tty is a stream
    PREP: Open slave side of pseudo tty
    PREP: Set O_NONBLOCK on write end of STREAM
    PREP: Put some messages on the STREAM
    TEST: Number of messages returned by ioctl
    ERROR: Message count incorrect
    Expected 7
    Received 6
    85 FAIL

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We don't see why pty-level flow control should prevent messages from
    getting to the head of the underlying STREAM. However we expect a protracted
    discussion will be needed to resolve this. So in the interests of expediency
    we recommend a Temporary Interpretation be granted, to be converted to
    a TSD or an MSF once a final resolution is arrived at.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    A Temporary Interpretation should be granted and the request also
    sent for a 14 day review.

    Review Type Expert Group Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    A waiver should be granted.

    XSH5 does not specify values for STREAMS device flow control
    parameters, but acknowledges that they do exist and says that calls to
    putmsg() and putpmsg() will block or return an error if flow control
    limits are reached (see XSH5 discussion on P674 last full paragraph
    continuing onto page 675). Similar discussion appears in the write()
    description on P1055 to 1056).
    The test is assuming that flow control will not happen without
    checking for that case.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion
    This is an agreed Test Suite Deficiency.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority