[LU-18362] expired_lock_main kernel thread should add lu_env to avoid LBUG

• Type: Bug
• Resolution: Duplicate
• Priority: Major
• Severity: 3
• Assignee: Shaun Tancheff
• Reporter: Shaun Tancheff

Description

expired_lock_main kernel thread should add lu_env to avoid observed LBUG:
.. (mdt_lvb.c:173:mdt_dom_lvbo_update()) ASSERTION( env ) failed:
.. (mdt_lvb.c:173:mdt_dom_lvbo_update()) LBUG
Pid: 863799, comm: ldlm_elt 4.18.0-305.10.2.x6.6.010.42.x86_64

mdt_dom_lvbo_update() uses lu_env_find() to acquire an lu_env instance and asserts if it is not available.

However an lu_env object was never added in the kthread so it is not surprising that it is not found via lu_env_find() leading to the above LBUG().

[expired_lock_main]
 - class_fail_export
   - mdt_obd_disconnect
     - mdt_mfd_close
       - mdt_dom_discard_data
         - ldlm_cli_enqueue_local
           - ldlm_lock_enqueue
             - ldlm_handle_conflict_lock
               - ldlm_run_ast_work
                 - ptlrpc_set_wait
                   - ptlrpc_check_set
                     - ldlm_cb_interpret
                       - ldlm_handle_ast_error
                         - mdt_dom_lvbo_update
                           - LASSERT(env)

Issue Links

• duplicates: LU-17668 mdt_dom_lvbo_update()) ASSERTION( env ) failed