IBM Support

PK66411: Through MVFS ? NFS, multithreaded file locking applications on multiprocessor RedHat Linux systems can cause a kernel panic

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Vendor Solution.

Error description

  • Through MVFS and remote VOBs and Views accessed by NFS, multithr
    eaded file locking applications which file lock against a single
     file on a multiprocessor RedHat Enterprise 4 Linux platform, ca
    n cause a kernel panic
    
    The panic backtrace is as follows:
    
    Call Trace:?ffffffff80190776?{locks_remove_posix+156} ?ffffffff8
    017be0d?{__fput+73}
           ?ffffffff8017aa0d?{filp_close+103} ?ffffffffa02824a5?{:mv
    fs:mvop_linux_close_kernel+41}
           ?ffffffffa02825b9?{:mvfs:mvop_linux_close+272} ?ffffffffa
    024f9db?{:mvfs:mvfs_closev_ctx+436}
           ?ffffffffa027ee44?{:mvfs:vnode_fop_release+121} ?ffffffff
    8017be27?{__fput+99}
           ?ffffffff8017aa0d?{filp_close+103} ?ffffffff80139f3d?{put
    _files_struct+101}
           ?ffffffff8013a76f?{do_exit+711} ?ffffffff801418ea?{recalc
    _sigpending+15}
           ?ffffffff80141e9b?{__dequeue_signal+458} ?ffffffff8013b25
    2?{sys_exit_group+0}
           ?ffffffff80143d39?{get_signal_to_deliver+1084} ?ffffffff8
    010f6fb?{do_signal+131}
           ?ffffffff8017a75b?{filp_open+105} ?ffffffff801f04e5?{strn
    cpy_from_user+74}
           ?ffffffff801102f3?{sysret_signal+28} ?ffffffff801105df?{p
    tregscall_common+103}
    
    
    Workaround:  None, unless the VOB and View storage is local to t
    he system
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • The problem is caused by a RedHat Linux kernel defect.
    

APAR Information

  • APAR number

    PK66411

  • Reported component name

    CLEARCASE UNIX

  • Reported component ID

    5724G2901

  • Reported release

    701

  • Status

    CLOSED ISV

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-05-20

  • Closed date

    2008-12-09

  • Last modified date

    2008-12-09

  • 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

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

Document Information

Modified date:
09 December 2008