Cluster Project tag, gfs-kernel_2_6_9_80, created. gfs-kernel_2_6_9_76-54-g10a84a8

Cluster Project tag, gfs-kernel_2_6_9_80, created. gfs-kernel_2_6_9_76-54-g10a84a8

[cfeist]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".

http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=10a84a86606dd6d5e30d0051e68c68cd9bbf2ea3

The tag, gfs-kernel_2_6_9_80 has been created
        at  10a84a86606dd6d5e30d0051e68c68cd9bbf2ea3 (commit)

- Log -----------------------------------------------------------------
commit 10a84a86606dd6d5e30d0051e68c68cd9bbf2ea3
Author: Abhijith Das <adas@redhat.com>
Date:   Fri May 9 12:00:05 2008 -0500

    gfs-kernel: Workaround fix for bz 444912 (gfs_glock_is_locked_by_me problem)
    
    This one-line fix, removes the assert warning. The behavior of the code is unchanged except that the assert warnings will no longer appear in the logs. This warning is tripped through the madvise syscall where control reaches the readpage function without the inode glock being held. We return -ENOSYS in such a case, disabling the madvise syscall.
    
    A more elegant fix for RHEL5 gfs that supports the madvise syscall (bz 429343) could not be ported to RHEL4 because AOP_TRUNCATED_PAGE is not available in RHEL4.
-----------------------------------------------------------------------


hooks/post-receive
--
Cluster Project