[LU-4524] ldlm_handle_enqueue0 incorrectly interprets ldlm_lock_create's NULL return value

• Type: Improvement
• Resolution: Fixed
• Priority: Major
• Fix Version/s: Lustre 2.6.0
• Affects Version/s: Lustre 2.6.0, Lustre 2.4.2, Lustre 2.5.1
• Assignee: Emoly Liu
• Reporter: Shuichi Ihara (Inactive)

Description

As described by John in LU-4034, ldlm_handle_enqueue0 assumes that NULL values from ldlm_lock_create are due to memory errors. In reality, there are other causes, such as ENOENT. The error reporting should be fixed as it causes confusion for sysadmins, and can waste time.

Logs from LU-4034:

Oct 1 16:20:11 zeus kernel: LustreError: 11-0: scratch-OST0013-osc-ffff8804925f1400: Communicating with 172.16.126.4@tcp, operation ldlm_enqueue failed with -12.
Oct 1 16:20:11 zeus kernel: LustreError: 23207:0:(cl_lock.c:1420:cl_unuse_try()) result = -12, this is unlikely!
Oct 1 16:20:11 scratch02 kernel: LustreError: 4630:0:(ldlm_resource.c:1165:ldlm_resource_get()) scratch-OST0013: lvbo_init failed for resource 0x40d9dcf:0x0: rc = -2

Issue Links

• is related to: LU-4970 Test failure sanity-lfsck test_14: ls should success
• is related to: LU-4230 Test failure on test suite replay-ost-single, subtest test_3