[LU-666] mdd depends on ldiskfs-only dynlocks feature

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.2.0
• Story Points: 1
• Severity: 3
• Bugzilla ID: 22,435

Epic

server

• Project: Orion
• Assignee: Lai Siyao
• Reporter: Brian Behlendorf

Description

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.

Issue Links

• Trackbacks: Changelog 2.2 version 2.2.0 Support for networks: o2iblnd OFED 1.5.4 Server support for kernels: 2.6.32220.4.2.el6 (RHEL6) Client support for unpatched kernels: 2.6.18274.18.1.el5 (RHEL5) 2.6.32220.4.2.el6 (RHEL6) 2.6.32.360....