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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0525 Actions

    Problem Report Number 0525
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0144
    Raised 1998-06-10 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Network File System
    Certification Program The Open Brand certification program
    Test Suite VSX4+XNFS version 4.4.2
    Test Identification POSIX.os/files/pathconf 38
    Problem Summary PG4R.145 Looking at NFS v3, which supports pathconf(2) with NFSPROC3_PATHCONF, the semantics of pathconf(2) look pretty clear. We are meant to return the characteristics of the filesystem on the server. But NF...
    Problem Text
    Looking at NFS v3, which supports pathconf(2) with NFSPROC3_PATHCONF,
    the semantics of pathconf(2) look pretty clear. We are meant to
    return the characteristics of the filesystem on the server. But
    NFS v2 gives us no means in general of finding out these
    characteristics. We think the right thing to do would be to fail
    (return -1) and also set errno to EINVAL. That is, treat
    _PC_NO_TRUNC and most of the others as unsupported options in NFS v2.
    We would question whether the test is correct in seeming to expect
    NFS v2 to support pathconf(2).

    Test Output
    200|0 38 22:13:38|TP Start
    520|0 38 00009802 1 1|pathconf(".", _PC_NO_TRUNC)
    did not give correct results
    520|0 38 00009802 1 2|expected: return value != -1
    520|0 38 00009802 1 3|observed: return value == -1,
    errno == 0 (NO ERROR)

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The cause of the problem is not entirely clear from the information provided.
    The following are possibilities:

    (1) The test suite is being executed in XPG4 mode rather than XPG3 mode.
    The release notes recommend that for XNFS testing, XPG3 mode should be
    used. In XPG3 mode the test would produce a NOTINUSE result.

    (2) The server file system does not have _POSIX_NO_TRUNC set and the call to
    pathconf() is using the NFSv3 protocol to obtain this information
    from the server. In this case the test is correct and the server
    needs to be set correctly. (_POSIX_NO_TRUNC is mandated for XPG4
    conformance).

    (3) The system is using the NFSv2 protocol and is, therefore, unable to
    obtain pathconf() information from the server. In this case, since
    _POSIX_NO_TRUNC is mandated for XPG4 conformance, the call to pathconf()
    should never return -1 in an XPG4 conforming environment.

    The XNFS specification states that the return value from a call to pathconf()
    need not accurately reflect the behavior of the server system. This suggests
    that the value provided by pathconf() may differ from the real value for the
    server system, but not that the call to pathconf() can provide an error
    indication of EINVAL because the file resides on an NFS server system.

    It is recommended 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