IBM Support

PM55142: RedHat Enterprise 6 kernel panics when executing an ls or find from within a view-extended path and not within a VOB

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible.

Error description

  • RedHat Enterprise 6 kernel panics when executing an ls or find
    from within a view-extended path and not within a VOB
    
    
    ClearCase 7.1.2.4
    
    RedHat Enterprise 6 and 6 SP1
    
    
    
    To Reproduce:
    
    
    1)  Start a view:  cleartool startview ?tag?
    
    2)  cd into /view/?tag?/var/empty
    
    3)  Issue either a Linux ?find? or Linux ?ls? command:  The
    following panic will occur:
    
    crash? bt
    PID: 12930  TASK: ffff8806ff2840c0  CPU: 0   COMMAND: 'find'
     #0 [ffff8806ba46b770] machine_kexec at ffffffff810310db
     #1 [ffff8806ba46b7d0] crash_kexec at ffffffff810b6332
     #2 [ffff8806ba46b8a0] oops_end at ffffffff814de840
     #3 [ffff8806ba46b8d0] no_context at ffffffff81040ccb
     #4 [ffff8806ba46b920] __bad_area_nosemaphore at
    ffffffff81040f55
     #5 [ffff8806ba46b970] bad_area_nosemaphore at ffffffff81041023
     #6 [ffff8806ba46b980] __do_page_fault at ffffffff810416dd
     #7 [ffff8806ba46baa0] do_page_fault at ffffffff814e084e
     #8 [ffff8806ba46bad0] page_fault at ffffffff814ddbd5
        [exception RIP: kern_addr_valid+194]
        RIP: ffffffff8103f802  RSP: ffff8806ba46bb88  RFLAGS:
    00010206
        RAX: 0000088904408000  RBX: ffff880d9f8b0100  RCX:
    00003ffffffff000
        RDX: 0000088904408fc0  RSI: ffff880000000000  RDI:
    8b08488904408b04
        RBP: ffff8806ba46bb88   R8: ffff8806fd77e940   R9:
    0000000000000000
        R10: 0000000000000100  R11: ffff8806ba46bc48  R12:
    ffff880a497f8b00
        R13: 00000000000000c0  R14: ffff880141defa78  R15:
    ffff8807005ac140
        ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
     #9 [ffff8806ba46bb90] kmem_ptr_validate at ffffffff81159b4e
    #10 [ffff8806ba46bbc0] d_validate at ffffffff8118a83e
    #11 [ffff8806ba46bbf0] vnode_dop_revalidate at ffffffffa04f593d
    [mvfs]
    #12 [ffff8806ba46bc90] do_lookup at ffffffff8118064a
    #13 [ffff8806ba46bcf0] __link_path_walk at ffffffff81180d79
    #14 [ffff8806ba46bd70] path_walk at ffffffff811816fa
    #15 [ffff8806ba46bdb0] do_path_lookup at ffffffff811818cb
    #16 [ffff8806ba46bde0] user_path_at at ffffffff81181a57
    #17 [ffff8806ba46beb0] vfs_fstatat at ffffffff81177d5c
    #18 [ffff8806ba46bef0] sys_newfstatat at ffffffff81177dc4
    #19 [ffff8806ba46bf80] system_call_fastpath at ffffffff8100b172
        RIP: 000000320d6d7faa  RSP: 00007fffd4bd5998  RFLAGS:
    00000202
        RAX: 0000000000000106  RBX: ffffffff8100b172  RCX:
    0000000000f1dabf
        RDX: 0000000000f1d118  RSI: 0000000000f1d1a8  RDI:
    ffffffffffffff9c
        RBP: 0000000000f1d118   R8: 0000000000000100   R9:
    0000000000800000
        R10: 0000000000000100  R11: 0000000000000246  R12:
    0000000000f18c90
        R13: 0000000000f1d0b0  R14: 0000000000000001  R15:
    0000000000f18c90
        ORIG_RAX: 0000000000000106  CS: 0033  SS: 002b
    
    The same backtrace is seen with the Linux ?ls? command as well.
    
    
    Workaround:  Do not access non-VOB related mounts when cd?ing
    into a view-extended path.  On Linux, the view-extended path
    will not cover objects that do not reside within MVFS and thus
    would require a setview shell to accommodate those types of file
    level access.  This restriction is due to a kernel level
    limitations on third party filesystems.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This problem is no longer reproducible by the customer once
    the kernel has been rebuilt.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM55142

  • Reported component name

    CC&CC MSITE WIN

  • Reported component ID

    5724G3300

  • Reported release

    712

  • Status

    CLOSED UR5

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-12-29

  • Closed date

    2012-06-05

  • Last modified date

    2012-06-05

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R712 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH3S","label":"Rational ClearCase MultiSite"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
05 June 2012