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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 0166 Actions

    Problem Report Number 0166
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0166
    Raised 1994-06-14 08:00
    Updated 2003-03-13 08:00
    Published 1994-06-20 08:00
    Product Standard Internationalised System Calls and Libraries (XPG4)
    Certification Program The Open Brand certification program
    Test Suite VSX4 version 4.3.4
    Test Identification XPG4.os/ipc/shmat 2
    Linked Problem Reports err.4.3.3.060, (in, old, system)
    Problem Summary TSD4.166 This was reported to vsx_support during the beta testing of VSX 4.3.3 and accepted as a test suite deficiency. The fix was not expected to make VSX 4.3.4. Below is the supportive information included ...
    Problem Text
    This was reported to vsx_support during the beta testing of VSX 4.3.3 and
    accepted as a test suite deficiency. The fix was not expected to make
    VSX 4.3.4. Below is the supportive information included with the
    original error report.

    The shmget() call fails in the output below due to the use of 2 * SHMLBA
    as the requested size of the shared memory segment. The XPG4 XSI defines
    SHMLBA as Segment low boundary address multiple. On our implementation
    SHMLBA is defined as 0x10000000, this is effectively the starting address
    of the first shared memory segment. However, this is unsuitable to use as a
    basis for the size. 0x10000000 converts to 268,435,456 bytes and twice
    that is greater than 536 MB. Our implementation only supports shared
    memory segments of less than or equal to 256 MB. Thus, the shmget() call
    fails because it is trying to request an shared memory segment greater
    than the maximum allowable on our system.


    vsx_support response:

    We are somewhat surprised by your value of SHMLBA! Please could you
    explain why it is so large? Typically it has a value similar to a
    page size, e.g. 4096.

    We can think of an alternative strategy that would only require an
    initial shmget() of SHMLBA bytes instead of 2*SHMLBA. This would prevent
    the EINVAL error, however we think execution of the test would require
    unreasonable resources when SHMLBA is very large.

    The alternative would be to stick with the current strategy but give an
    UNTESTED result if SHMLBA is unreasonably large.

    Test Output

    ***********************************************************************
    /tset/XPG4.os/ipc/shmat/T.shmat 2 Unresolved

    Test Description:
    When the calling process has read and write permission on the shared
    memory segment, the value of the SHM_RND bit is set in shmflg and the
    value of shmaddr is not zero, then a call to
    shmat(shmid,shmaddr,shmflg) attaches the segment for reading and
    writing at the address given by (shmaddr - (shmaddr modulus SHMLBA))
    and returns the segment start address.

    Test Information:
    shmget(key, 2*SHMLBA, mode|IPC_CREAT) failed with err 22
    ************************************************************************

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    This is accepted as a test suite fault and it is recommended that this
    be treated as a test suite deficiency.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion
    This is an agreed Test Suite Deficiency.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority