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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0500 Actions

    Problem Report Number 0500
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0119
    Raised 1995-08-08 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Internationalised System Calls and Libraries (XPG4)
    Certification Program The Open Brand certification program
    Test Suite VSX4 version 4.3.4
    Test Identification POSIX.os/files/chown 5
    Problem Summary PG4R.120 This test is failing because the test case is using '2147483647' as an out of range uid number and the IRIX6.2 file system code is returning EOVERFLOW. The VSX4 test suite is expecting EINVAL instea...
    Problem Text
    This test is failing because the test case is using '2147483647' as an out of
    range uid number and the IRIX6.2 file system code is returning EOVERFLOW.
    The VSX4 test suite is expecting EINVAL instead of EOVERFLOW (decimal 79).

    In IRIX6.2 '2147483647' is an invalid UID.

    We are asking that a waiver be granted because EOVERFLOW more closely describes
    the error within the SGI IRIX6.2 kernel file system code and that the X/Open
    document supports this case as it is unspecified as to which value errno is set
    to when more than one error condition exists, and it may not be possible to
    exercise all of the defined error conditions.

    The X/Open document:

    System Interfaces and Headers, Issue 4, Version 2;
    Section 2.3 Error Numbers, pages 25 through 30

    page 25:

    "If more than one error occurs in processing a function call, any one of"
    "the possible errors may be returned, as the order of detection is "
    "undefined."

    page 29: describes EOVERFLOW as:

    "UX [EOVERFLOW] Value too large to be stored in data type "
    " The user ID or group ID of an IPC or file system object"
    " was too large to be stored into appropriate member of "
    " caller-provided structure. This error will only occur "
    " on implementations that support a larger range of user "
    " ID or group ID values than the declared structure "
    " member can support. This usually occurs because the "
    " IPC or file system object resides on a remote machine "
    " with a larger value of the type uid_t, off_t or gid_t "
    " than the local system. "

    We think that EOVERFLOW applies to the error condition that is encountered
    within the SGI IRIX6.2 kernel file system code.
    Test Output
    /tset/POSIX.os/files/chown/T.chown 19 Failed

    Test Information:
    chown("chown-t.19", 0, 2147483647) did not give correct results
    ERRNO VALUES: expected: 22 (EINVAL), observed: 79 (UNKNOWN)
    chown("chown-t.19", 2147483647, 2001) did not give correct results
    ERRNO VALUES: expected: 22 (EINVAL), observed: 79 (UNKNOWN)

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The comments above relate to the fact that an additional error condition has
    appeared in the Single Unix specification which overlaps with error conditions
    that were previously defined in the XPG 4 and POSIX.1-1990 specifications.
    The commentary relating to the new error condition suggests that this relates
    to cases where networked heterogenous systems do not have a common size for
    members of structures like the stat structure. However, here we have a case
    where the system under test is a single machine environment which is addressed
    by the POSIX.1 specifications rather than a networked environment that is not
    addressed by the POSIX.1 standards. The POSIX.1 specification allows for a
    system which does not detect this error or for a system which detects the error
    and provides an EINVAL indication. While both POSIX.1 and XPG 4 allow for
    additional errors to be specified, they do not allow a different error condition
    to be indicated in the case that an error is already specified in their
    specifications.

    I conclude that, by granting this waiver, there would be a precedent of
    establishing an XPG 4 branded system which did not conform to POSIX.1.

    At the moment, I do not understand why this value has been assigned to the
    VSX_INVALID_UID configuration variable. I believe that the value should be
    set to "unsup" since the system does not support the detection of the EINVAL
    error condition in this situation.

    I recommend that this request is refused.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion
    This request is refused.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority