[LU-14618] when lov sub-lock initialization fails, LBUG: ASSERTION( (!(result == 0) || (nr == lovlck->lls_nr)) ) ensues Created: 16/Apr/21  Updated: 28/Mar/22  Resolved: 28/Mar/22

Status: Closed
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.15.0

Type: Bug Priority: Major
Reporter: Zhenyu Xu Assignee: Zhenyu Xu
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
is related to LU-15702 (lov_lock.c:206:lov_lock_sub_init()) ... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

When lov sub-lock initialization fails, lov_lock_sub_init() needs to handle the error correctly.

 Comments   
Comment by Gerrit Updater [ 16/Apr/21 ]

Bobi Jam (bobijam@hotmail.com) uploaded a new patch: https://review.whamcloud.com/43345
Subject: LU-14618 lov: correctly handling sub-lock init failure
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: ce7000598b610579b54a0074da55c0b5d9c07a99

Comment by Gerrit Updater [ 05/May/21 ]

Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/43345/
Subject: LU-14618 lov: correctly handling sub-lock init failure
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 1a5169f9962e254ed4225fe35e8ee6cb6ff7a7f6

Comment by Peter Jones [ 05/May/21 ]

Landed for 2.15

Comment by Etienne Aujames [ 02/Aug/21 ]

b2_12 backport: https://review.whamcloud.com/44467 ("LU-14618 lov: correctly handling sub-lock init failure")

Comment by John Hammond [ 28/Mar/22 ]

Re-closing this issue. Follow on work will be done in LU-15702.

Generated at Sat Feb 10 03:11:18 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.