From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Plugs race between the dc thread and an unlock ast message
Date: Tue, 09 Feb 2010 13:49:12 -0800 [thread overview]
Message-ID: <4B71D858.8050002@oracle.com> (raw)
In-Reply-To: <20100209205508.GF29766@redhat.com>
David Teigland wrote:
> BUG hit just five minutes after starting make_panic and alternate on four
> nodes. (I can send history before this if you need.)
>
Feb 9 14:09:52 bull-05 kernel: (6983,0,dlm_astd):
ocfs2_locking_ast:1104 lock M000000000000000009732800000000, action 2,
unlock 0, level 0, newlevel 5
ocfs2_unlock_ast:3075 UNLOCK AST called on lock
M000000000000000009732800000000, action = 2 (DROP_LOCK)
ocfs2_blocking_ast:1059 BAST fired for lockres
M000000000000000009732800000000, blocking 5, level -1 type Meta
ocfs2_generic_handle_bast:932 lockres M000000000000000009732800000000,
block 5, level -1, l_block 5, dwn 1
Feb 9 14:09:52 bull-05 kernel: (7009,2,ocfs2dc):
ocfs2_process_blocked_lock:4004 lockres M000000000000000009732800000000
blocked.
ocfs2_prepare_downconvert:3295 ERROR: lock
M000000000000000009732800000000, lvl -1 <= 0, blcklst 1, mask 1, type 0,
flags 0x104, h
So the BAST fires after the UNLOCK AST (DROP_LOCK). That is what
we thought.
Why does ocfs2_generic_handle_bast() not take into account the current
lockres->l_level?
next prev parent reply other threads:[~2010-02-09 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 18:16 [Ocfs2-devel] [PATCH] ocfs2: Plugs race between the dc thread and an unlock ast message Sunil Mushran
2010-02-04 10:27 ` Wengang Wang
2010-02-04 19:36 ` Sunil Mushran
2010-02-05 6:01 ` Joel Becker
2010-02-05 18:39 ` Sunil Mushran
2010-02-05 19:33 ` Mark Fasheh
2010-02-05 23:37 ` Sunil Mushran
2010-02-09 20:55 ` David Teigland
2010-02-09 21:49 ` Sunil Mushran [this message]
2010-02-05 16:24 ` David Teigland
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=4B71D858.8050002@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.