Whamcloud - gitweb
LU-666 mdd depends on ldiskfs-only dynlocks feature
authorBrian Behlendorf <behlendorf1@llnl.gov>
Wed, 24 Aug 2011 17:22:27 +0000 (10:22 -0700)
committerOleg Drokin <green@whamcloud.com>
Thu, 13 Oct 2011 19:31:29 +0000 (15:31 -0400)
commit69efa174743f5ad2425c0ccd951961ae356fed0d
treef74f44c9e31cd839388c5995de026e7daf6b1e5a
parent9cc7e09f24b6128ab871ff91e35cc8f6a46955e1
LU-666 mdd depends on ldiskfs-only dynlocks feature

As discussed in Lustre bugzilla 22435 dynlocks are provided by
the ldiskfs and are not a generic facility.  They should be
removed from the mdd-level to allow building --without-ldiskfs
per Andreas's comment in 22435:

  https://bugzilla.lustre.org/show_bug.cgi?id=22435#c3

This change converts the instances of "struct dynlock_handle *"
to a "void *" pointer which is safe because they are never
dereferenced at this level.

It also wraps the "struct dynlock" entry in the mdd_object with
MDD_DISABLE_PDO_LOCK.  This effectively limits all direct dynlock
usage to the !MDD_DISABLE_PDO_LOCK case which is unconditionally
disabled in the code.  Presumable this code will simply be removed
at some point which will fully resolve the issue.

Change-Id: I7c8d2fb04b31736782e5f6ea2ff6b631b475fb91
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-on: http://review.whamcloud.com/1348
Reviewed-by: wangdi <di.wang@whamcloud.com>
Reviewed-by: Liang Zhen <liang@whamcloud.com>
Reviewed-by: Mikhail Pershin <tappro@whamcloud.com>
Tested-by: Hudson
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Tested-by: Maloo <whamcloud.maloo@gmail.com>
lustre/mdd/mdd_internal.h
lustre/mdd/mdd_lock.c