EX-7849 quota: notify newest lqe in qmt_set_id_notify

EX-7849 quota: notify newest lqe in qmt_set_id_notify

It is possible that lqe_locate may call lqe_find inside
qmt_pool_lqes_lookup_spec and insert the 2nd lqe into
lqs_hash during processing the previous one. Do not add the
1st lqe to be processed by qmt_reba_thread in qmt_id_lock_notify,
as this lqe will be freed in the end of lqe_locate_find due
to the race with the 2nd that is already exist in lqs_hash.
This fix should potentially fix the following assertion:

  (qmt_lock.c:950:qmt_id_lock_glimpse()) ASSERTION( lqe->lqe_gl ) failed:
  (qmt_lock.c:950:qmt_id_lock_glimpse()) LBUG

Lustre-change: https://review.whamcloud.com/53637
Lustre-commit: 2832874970232fb5e1deedbf89b7a482518e6886

Test-Parameters: trivial testlist=sanity-quota,racer
Test-Parameters: trivial testlist=sanity-quota,racer
Test-Parameters: trivial testlist=sanity-quota,racer
Test-Parameters: trivial testlist=sanity-quota,racer
Test-Parameters: trivial testlist=sanity-quota,racer
Test-Parameters: trivial testlist=sanity-quota,racer
Test-Parameters: trivial testlist=sanity-quota,racer
Test-Parameters: trivial testlist=sanity-quota,racer
Fixes: 09f9fb3211 ("LU-11023 quota: quota pools for OSTs")
Signed-off-by: Sergey Cheremencev <scherementsev@ddn.com>
Change-Id: I179edb06ec8c784636f566ffeba0035c6758a55b
Reviewed-on: https://review.whamcloud.com/c/ex/lustre-release/+/53496
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>