Whamcloud - gitweb
LU-2901 ldlm: fix resource/fid check, use DLDLMRES 92/6592/5
authorAndreas Dilger <andreas.dilger@intel.com>
Fri, 7 Jun 2013 22:31:51 +0000 (16:31 -0600)
committerOleg Drokin <oleg.drokin@intel.com>
Mon, 22 Jul 2013 22:32:45 +0000 (22:32 +0000)
commita1052417b78bc18898161c4ed44d79de4a1a2f23
tree99ee9728193392b6093f0b32bd339f2ab180edc6
parent7cd460776da349643f53cda4c5d4e927316b666e
LU-2901 ldlm: fix resource/fid check, use DLDLMRES

In ll_md_blocking_ast() the FID/resource comparison is incorrectly
checking for fid_ver() stored in res_id.name[2] instead of name[1]
changed since http://review.whamcloud.com/2271 (commit 4f91d5161d00)
landed.  This does not impact current clients, since name[2] and
fid_ver() are always zero, but it could cause problems in the future.

In ldlm_cli_enqueue_fini() use ldlm_res_eq() instead of comparing
each of the resource fields separately.

Use DLDLMRES/PLDLMRES when printing resource names everywhere.

Signed-off-by: Andreas Dilger <andreas.dilger@intel.com>
Signed-off-by: Lai Siyao <lai.siyao@intel.com>
Change-Id: I7b45d382d2ee87c1df813ebdd9c7f21029500c1e
Reviewed-on: http://review.whamcloud.com/6592
Tested-by: Hudson
Tested-by: Maloo <whamcloud.maloo@gmail.com>
Reviewed-by: Johann Lombardi <johann.lombardi@intel.com>
lustre/ldlm/ldlm_request.c
lustre/ldlm/ldlm_resource.c
lustre/liblustre/namei.c
lustre/llite/namei.c
lustre/mdc/mdc_locks.c
lustre/mdt/mdt_handler.c
lustre/mgc/mgc_request.c