[LU-14618] when lov sub-lock initialization fails, LBUG: ASSERTION( (!(result == 0) || (nr == lovlck->lls_nr)) ) ensues

• Type: Bug
• Resolution: Fixed
• Priority: Major
• Fix Version/s: Lustre 2.15.0
• Severity: 3
• Assignee: Zhenyu Xu
• Reporter: Zhenyu Xu

Description

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

Issue Links

• is related to: LU-15702 (lov_lock.c:206:lov_lock_sub_init()) ASSERTION( (!(result == 0) || (nr == lovlck->lls_nr)) ) failed:

Comments

[John Hammond]

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

[Etienne Aujames]

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

[Peter Jones]

Landed for 2.15

[Gerrit Updater]

Oleg Drokin ([e-mail]) 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

[Gerrit Updater]

Bobi Jam ([e-mail]) 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