This is the mail archive of the
cluster-cvs@sourceware.org
mailing list for the cluster.
Cluster Project tag, ccs_1_0_12, created. gfs-kernel_2_6_9_76-5-gb95f5dd
- From: cfeist at sourceware dot org
- To: cluster-cvs at sources dot redhat dot com, cluster-devel at redhat dot com
- Date: 3 Mar 2008 22:56:14 -0000
- Subject: Cluster Project tag, ccs_1_0_12, created. gfs-kernel_2_6_9_76-5-gb95f5dd
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=b95f5dd435df474b5b5c55927ae86b52f21c0b28
The tag, ccs_1_0_12 has been created
at b95f5dd435df474b5b5c55927ae86b52f21c0b28 (commit)
- Log -----------------------------------------------------------------
commit b95f5dd435df474b5b5c55927ae86b52f21c0b28
Author: David Teigland <teigland@redhat.com>
Date: Thu Feb 28 09:49:26 2008 -0600
lock_dlm: skip busy plocks in unlock
bz 432707
Another problem with multiple threads manipulating the same
plocks (also see bz 383391). In this case thread1 was waiting
on a plock that was in the dlm, when thread2 came and tried to
unlock it (due to the process exiting and closing all files).
dlm returns EBUSY for the unlock, which causes lock_dlm to assert
(another work around could be to just not assert on EBUSY.)
The "busy" flag was recently added to plocks to work around
another similar problem with multiple threads; use that to
just skip the unlock on any plock that's busy.
-----------------------------------------------------------------------
hooks/post-receive
--
Cluster Project