Whamcloud - gitweb
- Do the LOCK_CHANGED work in ldlm_lock_enqueue inside an ns_lock; it was making
authorpschwan <pschwan>
Tue, 4 Feb 2003 19:34:19 +0000 (19:34 +0000)
committerpschwan <pschwan>
Tue, 4 Feb 2003 19:34:19 +0000 (19:34 +0000)
commit207fbec5262efa1ef46d200abc3cb9bf6d1be0f5
treef21f6756c9dfb9e5b295fb1927ca1d9a78806c93
parentb1927b1827c46b23199926968bce0ebfcddf38be
- Do the LOCK_CHANGED work in ldlm_lock_enqueue inside an ns_lock; it was making
  me nervous without.
- The lock may have already received a blocking AST, while it was still owned
  by the server.  In this case, the client will receive the lock, oblivious to
  the fact that it needs to be given up.  Unset the "AST already sent" flag
  before handing the lock to the client.
- Add mdc_sem calls around ldlm_cli_enqueue in mdc_request
lustre/tests/rename.pl