From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] dlm: Fix spin lock already unlocked bug
Date: Tue, 2 Jan 2007 09:12:49 -0600 [thread overview]
Message-ID: <20070102151249.GA13513@redhat.com> (raw)
In-Reply-To: <459A69A0.5070003@redhat.com>
On Tue, Jan 02, 2007 at 02:18:08PM +0000, Patrick Caulfield wrote:
> >From the "how the hell did that get in there" collection.
>
> I just noticed this message when testing some other changes I'd made to
> lowcomms (to use workqueues) but the problem seems to be in the current
> git trees too. I'm amazed no-one has seen it.
>
> BUG: spinlock already unlocked on CPU#1, dlm_recoverd/16868
>
> Please check this before committing it someone (everyone?), in case I'm
> hallucinating after all the christmas punch ;-)
Looks good to me (haven't seen it since my test machines are UP). The
spin_locks are in the RHEL5 code, I'm not sure how they disappeared
upstream.
next prev parent reply other threads:[~2007-01-02 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 14:18 [Cluster-devel] [PATCH] dlm: Fix spin lock already unlocked bug Patrick Caulfield
2007-01-02 15:01 ` Robert Peterson
2007-01-02 15:12 ` David Teigland [this message]
2007-01-02 17:08 ` Patrick Caulfield
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=20070102151249.GA13513@redhat.com \
--to=teigland@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 NNTP newsgroup(s).