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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0435 Actions

    Problem Report Number 0435
    Submitter's Classification Specification problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0054
    Raised 1994-04-18 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.3.3
    Test Identification XNFS.prtl/proto/readlnk 2
    Problem Summary PG4R.054 This test is trying to perform a readlink on a regular file (non-link file). XNFS defines that NFSERR_NXIO (errno 6) should be returned when a file handle does not refer to a symbolic link. However, o...
    Problem Text
    This test is trying to perform a readlink on a regular file (non-link file).

    XNFS defines that NFSERR_NXIO (errno 6) should be returned when a
    file handle does not refer to a symbolic link. However, our base operating
    system complies with System V SVID 3 which states that a readlink of
    a non-symblolic link should return EINVAL (error 22). It seems that these
    standards do not match for the readlink call.
    Test Output
    15|0 2.0b 1|TCM Start
    400|0 2 1 10:13:43|IC Start
    200|0 2 10:13:43|TP Start
    520|0 2 00011066 1 1|NFSPROC_READLINK returned incorrect status
    520|0 2 00011066 1 2|expected <6> actual <22>

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The NFSPROC_READLINK protocol is expected to return the the error condition
    NFSERR_NXIO when the referenced file is not a symbolic link. Both the SVID
    3 and latest drafts of POSIX.1 state that the error condition for the readlink()
    API is EINVAL when the referenced file is not a symbolic link.

    While there is a recognised difference between these statements, this can
    be resolved by introducing a mapping between the protocol layer and the
    API layer. This does not seem to be a grey area and a permanent interpretation
    is not recommended.

    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