public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: cfeist@sourceware.org
To: cluster-cvs@sources.redhat.com, cluster-devel@redhat.com
Subject: Cluster Project tag, gfs-kernel_2_6_9_77, created. gfs-kernel_2_6_9_76-5-gb95f5dd
Date: Mon, 10 Mar 2008 22:49:00 -0000	[thread overview]
Message-ID: <20080310224928.18096.qmail@sourceware.org> (raw)

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, gfs-kernel_2_6_9_77 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


                 reply	other threads:[~2008-03-10 22:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080310224928.18096.qmail@sourceware.org \
    --to=cfeist@sourceware.org \
    --cc=cluster-cvs@sources.redhat.com \
    --cc=cluster-devel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).