Linux ocfs2 filesystem development
 help / color / mirror / Atom feed
From: Wengang Wang <wen.gang.wang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] avoid being purged when queued for assert_master
Date: Wed, 12 Oct 2011 15:04:33 +0800	[thread overview]
Message-ID: <20111012070433.GA11852@laptop.jp.oracle.com> (raw)

Hi Sunil/Joel/Mark and anyone who has interest,

This is not a patch but a discuss.

Currently we have a problem:
When a lockres is still queued(in dlm->work_list) for sending an
assert_master(or in processing of sending), the lockres can't be
purged(removed from hash). there is no flag/state,on lockres its self,dinotes
this situation.

The badness is that if the lockres is purged(surely not the owner at the
moment), and the assert_master is after the purge. it can confuse other
nodes. On another node, the owner now can be any other nodes, thus on
receiving the assert_master, it can trigger a BUG() because 'owner'
doesn't match.

So we'd better to prevent the lockres from be purged when it's queued
for something(assert_master).

Srini and I discussed some possible fixes:
1) adding a flag to lockres->state.
   this does not work. A lockres can have multiple instances in the queue list.
   A simple flag is not safe. And the instances are not nested, so even
   saving a previous flags doesn't work. Neither can we merge the instances
   because they can be for different purposes.

2) checking if the lockres if queued before purging it.
  this works, but doesn't sounds good. it needs changes of current behaviour
  on the queue list.   Also, we have no idea on the performance of the checking
  (searching list).

3) making use of lockres->inflight_locks.
  this works, but seems to be a mis-use of inflight_locks.

4) adding a new member to lockres counting the queued time.
   this works and simple. but needs extra memory.

I prefer to the 4).

What's your idea?

thanks,
wengang.

             reply	other threads:[~2011-10-12  7:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12  7:04 Wengang Wang [this message]
2011-10-13  0:32 ` [Ocfs2-devel] avoid being purged when queued for assert_master Sunil Mushran
2011-10-13  1:02   ` Wengang Wang
2011-10-13  1:47     ` Sunil Mushran
2011-10-13  1:51       ` Wengang Wang
2011-10-13  2:07         ` Wengang Wang
2011-10-13  2:11           ` Sunil Mushran
2011-10-13  2:13             ` Wengang Wang
2011-10-13 16:09               ` Sunil Mushran
2011-10-13 23:35                 ` Wengang Wang
2011-10-13 23:37                   ` Sunil Mushran
2011-10-14  0:19                     ` Wengang Wang
2011-10-14  0:23                       ` Wengang Wang
2011-10-14  0:25                       ` Sunil Mushran
2011-10-14  8:57                         ` Wengang Wang
2011-10-14 17:56                           ` Sunil Mushran
2011-10-15 10:58                             ` Wengang Wang

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=20111012070433.GA11852@laptop.jp.oracle.com \
    --to=wen.gang.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox