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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 2564 Actions

    Problem Report Number 2564
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0284
    Raised 2011-03-10 05:11
    Updated 2011-03-30 07:29
    Published 2011-03-30 07:29
    Product Standard Internationalised System Calls and Libraries Extended V3 (UNIX 03)
    Certification Program The Open Brand certification program
    Test Suite VSRT version 5.4.3
    Test Identification POSIX_rte.os/procprim/posix_spawnp/T.posix_spawnp.58
    Specification Base Definitions Issue 6
    Linked Problem Reports PR, 2562
    Problem Summary POSIX_rte.os/procprim/posix_spawnp/T.posix_spawnp test 58 fails due to not
    reporting EBADF when closing an already closed fd
    Problem Text The current test does not reflect the change documented in Austin Group
    Defect 370:
    0000370: addclose should not cause posix_spawn to fail if closing an
    already closed fd
    which clarifies that closing an already closed fd should not result in
    EBADF. While that change is implemented in Issue 7, it would appear
    clear that reporting EBADF due to closing an already closed fd was not
    the intent and is not the desired action going forward.

    This is essentially the same issue documented in PR 2562, but in this
    instance the problem hits the posix_spawnp test.
    Test Output **********************************************************************************************************************************************
    /tset/POSIX_rte.os/procprim/posix_spawnp/T.posix_spawnp 58 Failed

    Test Description:
    If the symbol {_POSIX_SPAWN} is defined or the implementation supports
    the posix_spawnp(pid, file, file_actions, attrp, argv[], envp[])
    function:
    When file_actions contains an close action and fildes is not a
    valid file descriptor, then posix_spawnp(pid, file, file_actions,
    attrp, argv[], envp[]) returns EBADF or posix_spawnp(pid, file,
    file_actions, attrp, argv[], envp[]) returns zero and the child
    process exits with an exit status of 127.

    Test Information:
    posix_spawnp returned 0 err 9 EBADF and child return 0

    **********************************************************************************************************************************************

    Review Information

    Review Type TSMA Review
    Start Date 2011-03-10 05:11
    Last Updated 2011-03-10 11:20
    Completed 2011-03-10 11:20
    Status Complete
    Review Recommendation Rejected (REJ)
    Review Response Austin Group Defect 370 is currently just a proposed change to be made
    in the next revision of the standard. In this form, it will not have
    any effect on the requirements of the standard until that revision
    (Issue 8) is approved.

    If implementors wish to be able to make this change to their systems
    before Issue 8 is approved, they should ask the Austin Group to reopen
    defect 370 and process it as an interpretation with a response
    containing the key phrase "concerns have been raised about this which
    are being referred to the sponsor".

    Review Type SA Review
    Start Date 2011-03-10 19:20
    Last Updated 2011-03-23 11:03
    Completed 2011-03-23 11:03
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion The bug references Austin Group Defect 370 which is currently just a
    proposed change to be made in the next revision of the standard. As such
    it does not have any effect on the requirements of the standard until
    that revision (Issue 8) is approved.

    In order to make the proposed change applicable to Issue 7, it would
    need to be an interpretation against the current standard with a defect
    categorization. The submitter is thus recommended to make a request to
    the Austin Group to reopen defect 370 and process it as an
    interpretation with a response containing the key phrase "concerns have
    been raised about this which are being referred to the sponsor".

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority