cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] libdlm dlm_ls_lock_wait() doesn't.
Date: Wed, 19 Mar 2008 15:35:11 -0700	[thread overview]
Message-ID: <20080319223511.GB23815@mail.oracle.com> (raw)

Folks,
	Another problem I've run into with libdlm - call
dlm_ls_lock_wait() on a lock that another node holds, and it returns
instead of blocking.  This is not a trylock (LKF_NOQUEUE).  Trylocks
work as expected.  A blocking lock attempt does not block, it just
fails.  I haven't had the time to nail it yet, so if you get there
first, excellent.

Joel

-- 

"We'd better get back, `cause it'll be dark soon,
 and they mostly come at night.  Mostly."

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127



             reply	other threads:[~2008-03-19 22:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 22:35 Joel Becker [this message]
2008-03-20 14:39 ` [Cluster-devel] libdlm dlm_ls_lock_wait() doesn't David Teigland
2008-03-20 21:45   ` Joel Becker
2008-03-20 22:20     ` Joel Becker

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=20080319223511.GB23815@mail.oracle.com \
    --to=joel.becker@oracle.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 NNTP newsgroup(s).