PM81826: Running lsof on /proc/locks causes kernel panic on SLES 10

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When you run 'lsof /proc/locks' on a Suse Linux Enterprise
    System 10 server with IBM Rational ClearCase MVFS installed, you
    experience a kernel panic.
    
    The backtrace looks similar to the following:
    
     #0 [ffff8117725d7a90] machine_kexec at ffffffff8011c17e
     #1 [ffff8117725d7b60] crash_kexec at ffffffff80154783
     #2 [ffff8117725d7c20] __die at ffffffff802f1ad8
     #3 [ffff8117725d7c60] do_page_fault at ffffffff802f33e1
     #4 [ffff8117725d7d60] error_exit at ffffffff8010bced
        [exception RIP: lock_get_status+26]
        RIP: ffffffff8019ae26  RSP: ffff8117725d7e18  RFLAGS:
    00010286
        RAX: 0000000000000000  RBX: ffff81104f90e031  RCX:
    ffffffff80318838
        RDX: 0000000000000002  RSI: ffff810be16c4818  RDI:
    ffff81104f90e031
        RBP: ffff810be16c4818   R8: ffff81104f90e000   R9:
    0000000000000002
        R10: 0000000000000000  R11: ffff810c0c000d00  R12:
    0000000000000000
        R13: ffff81104f90e000  R14: 0000000000000000  R15:
    ffff810be16c4818
        ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
     #5 [ffff8117725d7e30] get_locks_status at ffffffff8019c3b4
     #6 [ffff8117725d7e90] locks_read_proc at ffffffff801c1a06
     #7 [ffff8117725d7eb0] proc_file_read at ffffffff801c0332
     #8 [ffff8117725d7f10] vfs_read at ffffffff801874d8
     #9 [ffff8117725d7f40] sys_read at ffffffff801878b8
    #10 [ffff8117725d7f80] system_call at ffffffff8010ae16
        RIP: 00002aaaaac7a640  RSP: 00007fffffff85c8  RFLAGS:
    00010202
        RAX: 0000000000000000  RBX: ffffffff8010ae16  RCX:
    0000000000418dd3
        RDX: 0000000000000400  RSI: 00002aaaaaac9000  RDI:
    0000000000000003
        RBP: 00007fffffff85f0   R8: 00000000ffffffff   R9:
    0000000000000000
        R10: 0000000000000022  R11: 0000000000000246  R12:
    0000000000000fff
        R13: 0000000000000000  R14: 0000000000535a70  R15:
    0000000000535a70
        ORIG_RAX: 0000000000000000  CS: 0033  SS: 002b
    
    
    Workaround: Do not use lsof on affected systems.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Linux systems could panic if you run lsof on /proc/locks
    

Problem conclusion

  • A fix is available in ClearCase versions 7.1.2.11 and
    8.0.0.7
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM81826

  • Reported component name

    CLRCASE MSITE W

  • Reported component ID

    5724G3200

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-31

  • Closed date

    2013-06-27

  • Last modified date

    2013-06-27

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

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

Fix information

  • Fixed component name

    CLRCASE MSITE W

  • Fixed component ID

    5724G3200

Applicable component levels

  • R800 PSN

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Rational ClearCase MultiSite

Software version:

8.0

Reference #:

PM81826

Modified date:

2013-06-27

Translate my page

Machine Translation

Content navigation