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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1672 Actions

    Problem Report Number 1672
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0476
    Raised 2000-12-21 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Internationalised System Calls and Libraries Extended V2 (UNIX 98)
    Certification Program The Open Brand certification program
    Test Suite VSU version 5.1.1
    Test Identification CAPI.os/files/chmod 9
    Problem Summary PG4U.00179 These tests give an unresolved result if user vsx0 cannot create files in the root directory of the VSX_NOSPC_DEV file system.
    Problem Text
    The following assertions also fail for the same reason:

    /tset/CAPI.os/files/fchown/T.fchown 8 Unresolved
    /tset/CAPI.os/files/fstatvfs/T.fstatvfs 10 Unresolved
    /tset/CAPI.os/files/fstatvfs/T.fstatvfs 13 Unresolved
    /tset/CAPI.os/files/fstatvfs/T.fstatvfs 14 Unresolved
    /tset/CAPI.os/files/fstatvfs/T.fstatvfs 15 Unresolved
    /tset/CAPI.os/files/ftruncate/T.ftruncate 19 Unresolved
    /tset/CAPI.os/files/lchown/T.lchown 18 Unresolved
    /tset/CAPI.os/files/mknod/T.mknod 19 Unresolved
    /tset/CAPI.os/files/mknod/T.mknod 27 Unresolved
    /tset/CAPI.os/files/statvfs/T.statvfs 10 Unresolved
    /tset/CAPI.os/files/statvfs/T.statvfs 13 Unresolved
    /tset/CAPI.os/files/statvfs/T.statvfs 14 Unresolved
    /tset/CAPI.os/files/statvfs/T.statvfs 15 Unresolved
    /tset/CAPI.os/files/symlink/T.symlink 5 Unresolved
    /tset/CAPI.os/files/symlink/T.symlink 16 Unresolved
    /tset/CAPI.os/files/symlink/T.symlink 17 Unresolved
    /tset/CAPI.os/files/symlink/T.symlink 18 Unresolved
    /tset/CAPI.os/files/truncate/T.truncate 20 Unresolved
    /tset/CAPI.os/files/utimes/T.utimes 13 Unresolved
    /tset/CAPI.os/ioprim/writev/T.writev 56 Unresolved
    /tset/CAPI.os/sockets/bind/T.bind 21 Unresolved

    The failure occurs because when /tmp/mpoint is mounted R/W during
    test setup, it is mounted with permissions 755 and owned by root.
    When vsx0 tries to create the files necessary for the test to run,
    it does not have permissions to do so.

    The case for mounting R/W in vsu_mount.c is:

    case 2:
    /*mount device_name on dir_name read/write*/
    errno=0;
    ret=mnt_rw(device_name,dir_name);
    /* if fails, try to unmount and then retry */
    if (ret == -1) {
    (void) unmnt(device_name, dir_name);
    errno=0;
    ret=mnt_rw(device_name,dir_name);
    }
    if (ret == -1)
    if (errno != 0)
    leave(errno);
    else
    leave(254);
    else {
    /* Don't chmod(dir_name, S_IRWXU|S_IRWXG|S_IRWXO); */
    chmod(dir_name, S_IRWXU|S_IRWXG|S_IRWXO);
    leave(0);
    }

    The line where the chmod would have happened is commented out for some
    reason.

    If you look back to VSU 5.0.4 at the same part of the code:

    case 2:
    /*mount device_name on dir_name read/write*/
    errno=0;
    #ifdef FSINDEPMOUNT
    ret=mount(device_name, dir_name, MS_FSS, sysfs(GETFSIND, __FSTYP
    E),NULL,0);
    #else
    ret=mount(device_name,dir_name,0);
    #endif
    /* if fails, try to unmount and then retry */
    if (ret == -1) {
    (void) umount(device_name);
    errno=0;
    #ifdef FSINDEPMOUNT
    ret=mount(device_name, dir_name, MS_FSS, sysfs(GETFSIND,
    __FSTYPE),NULL,0);
    #else
    ret=mount(device_name,dir_name,0);
    #endif
    }
    if (ret == -1)
    if (errno != 0)
    if (errno != 0)
    leave(errno);
    else
    leave(254);
    else {
    chmod(dir_name, S_IRWXU|S_IRWXG|S_IRWXO);
    leave(0);
    }

    Here the chmod is happening.

    Is the commenting out of that line in the new code an accident or
    perhaps that functionality was intended to be moved to a different
    area of the code?

    If the line is put uncommented, and the test re-built and run, the
    tests work properly.

    Test Output
    ************************************************************************
    /tset/CAPI.os/files/fchmod/T.fchmod 9 Unresolved

    Test Description:
    Base Required Deviance
    EROFS in errno and return -1 on a call to int fchmod(int fildes,
    mode_t mode) when the file referenced by fildes resides on a read-only
    file system.

    Test Information:
    PREP: Mount file-system read-write on ../tmp/mpoint
    PREP: Create files and directories
    ERROR: mkdir for ../tmp/mpoint/rofs_testdir failed, errno = 13(EACCES -
    Permission denied)

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

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    These failures can be avoided by setting appropriate ownership and/or
    permissions for the root directory of the VSX_NOSPC_DEV file system
    before running the tests. The VSU user guide needs to be updated to
    document this as an additional requirement for the VSX_NOSPC_DEV file
    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