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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0324 Actions

    Problem Report Number 0324
    Submitter's Classification Specification problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0040
    Raised 1994-06-16 08:00
    Updated 2003-03-13 08:00
    Published 1994-06-20 08:00
    Product Standard Network File System
    Certification Program The Open Brand certification program
    Test Suite VSX4+XNFS version 4.3.4
    Test Identification XNFS.prtl/proto/nlm 9,10
    Specification Protocols for X/Open Interworking: XNFS, Issue 4
    Location in Spec See Problem Text
    Problem Summary PIN4.040 These failures are addressed in the "Release Notes for VSX+XNFS, Release 4.3.4" document. They are listed under the heading "Unresolved Grey Areas in the XNFS Specification". In these tests, captain.u...
    Problem Text
    These failures are addressed in the "Release Notes for VSX+XNFS, Release 4.3.4"
    document. They are listed under the heading "Unresolved Grey Areas in the
    XNFS Specification". In these tests, captain.unx.dec.com is the server
    machine name and drew.unx.dec.com is the client machine name. We feel that
    this is the proper use of the caller_name field.
    Test Output
    ************************************************************************
    /tset/XNFS.prtl/proto/nlm/T.nlm 9 Failed

    Test Description:
    If the Network Lock Manager is supported:
    When nlm_lockargs.reclaim is FALSE and nlm_lockargs.block is TRUE
    and there is an existing lock corresponding to file and region
    specified in nlm_lockargs.alock and the existing lock has the
    exclusive flag set to TRUE, then a call to
    NLM_LOCK_MSG(nlm_lockargs) returns nothing and causes a callback
    to the client of NLM_LOCK_RES(nlm_res) with LCK_BLOCKED in
    nlm_res.stat and when the request can be granted will cause a
    callback to the client of NLM_GRANTED_MSG(nlm_testargs).

    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 FALSE and
    block TRUE
    VERIFY that the server generates NLM_LOCK_RES
    VERIFY that the returned status is LCK_BLOCKED
    SERVER:
    UNLOCK file using fcntl
    CLIENT:
    VERIFY that the server generates NLM_GRANTED_MSG
    VERIFY that the returned lock matches the request
    CALL NLM_GRANTED_RES
    SERVER:
    UNLINK file

    Test Information:
    NLM_GRANTED_MSG had caller_name = "captain.unx.dec.com" instead of
    "drew.unx.dec.com".
    Path tracing error: expected 8 got 7
    ************************************************************************
    /tset/XNFS.prtl/proto/nlm/T.nlm 10 Failed

    Test Description:
    If the Network Lock Manager is supported:
    When nlm_lockargs.reclaim is FALSE and nlm_lockargs.block is TRUE
    and there is an existing lock corresponding to file and region
    specified in nlm_lockargs.alock and nlm_lockargs.exclusive is set
    to TRUE, then a call to NLM_LOCK_MSG(nlm_lockargs) returns nothing
    and causes a callback to the client of NLM_LOCK_RES(nlm_res) with
    LCK_BLOCKED in nlm_res.stat and when the request can be granted
    will cause a callback to the client of
    NLM_GRANTED_MSG(nlm_testargs).

    Test Strategy:
    SERVER:
    CREATE file
    LOCK non-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
    SERVER:
    UNLOCK file using fcntl
    CLIENT:
    VERIFY that the server generates NLM_GRANTED_MSG
    VERIFY that the returned lock matches the request
    CALL NLM_GRANTED_RES
    SERVER:
    UNLINK file

    Test Information:
    NLM_GRANTED_MSG had caller_name = "captain.unx.dec.com" instead of
    "drew.unx.dec.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
    This is a recognised grey area and a permanent interpretation is recommended.

    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