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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0346 Actions

    Problem Report Number 0346
    Submitter's Classification Specification problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0062
    Raised 1998-11-26 08:00
    Updated 2003-03-13 08:00
    Published 1998-11-27 08:00
    Product Standard Network File System
    Certification Program The Open Brand certification program
    Test Suite VSX4+XNFS version 4.4.3
    Test Identification XNFS.prtl/proto/nlm 12
    Specification Protocols for X/Open Interworking: XNFS, Issue 4
    Location in Spec See Problem Text
    Problem Summary PIN4.062 In the above three test suite failures, I understand that test suites 9 and 10 are already mentioned in the Release Notes ("Unresolved Grey Areas in the XNFS Specification") and have a permanent inter...
    Problem Text
    In the above three test suite failures, I understand that test suites 9 and 10
    are already mentioned in the Release Notes ("Unresolved Grey Areas in the XNFS
    Specification") and have a permanent interpretation (PIN4.040).

    However, test 12 is failing for the same reason that tests 9 and 10 are
    failing with regard to the caller_name field. I believe that a separate
    Interpretation is required for test 12 to cover the same problem that is
    occurring.
    Test Output
    ************************************************************************
    /tset/XNFS.prtl/proto/nlm/T.nlm 12 Failed

    Test Description:
    If the Network Lock Manager is supported:
    When nlm_canargs.block and nlm_canargs.exclusive and
    nlm_canargs.alock do not exactly match an outstanding blocked
    NLM_LOCK_MSG request, then a call to NLM_CANCEL_MSG(nlm_canargs)
    causes a callback to the client of NLM_CANCEL_RES(nlm_res) with
    LCK_DENIED in nlm_res.stat.

    Test Strategy:
    SERVER:
    CREATE file
    LOCK exclusively a portion of file using fcntl
    CLIENT:
    OBTAIN handle for file using NFSPROC_LOOKUP
    CALL NLM_LOCK_MSG for the portion of file with exclusive TRUE and
    block TRUE
    VERIFY that the server generates NLM_LOCK_RES
    VERIFY that the returned status is LCK_BLOCKED
    CALL NLM_CANCEL_MSG for a different potion of file
    VERIFY that the sever generates NLM_CANCEL_RES
    VERIFY that the returned status is LCK_DENIED
    SERVER:
    UNLOCK file using fcntl
    UNLINK file

    Test Information:
    NLM_GRANTED_MSG had caller_name = "xmk2.london.sco.com" instead of
    "sconix.london.sco.com".
    Path tracing error: expected 8 got 7

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

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We agree that this problem is caused by the same situation as
    for test cases 9 and 10. We recommend that a Permanent Interpretation
    be granted for this test, as was the case for test cases 9 and 10
    (see PIN4.040).

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Permanent Interpretation (PIN)
    Review Conclusion
    A Permanent Interpretation is granted.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority