[LU-14070] consider recovering case in tgt_brw_unlock()) assertions Created: 23/Oct/20 Updated: 03/Nov/20 Resolved: 03/Nov/20 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.14.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Mikhail Pershin | Assignee: | Mikhail Pershin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Severity: | 3 | ||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
During recovery the tgt_brw_lock() doesn't take locks in all cases but tgt_brw_unlock() is not taking that in consideration when doing assertion checks. As result we might get the following false assertion: tgt_handler.c:1728:tgt_brw_unlock()) ASSERTION( (obj->ioo_bufcnt > 0 && (niob[0].rnb_flags & 0x200)) == lustre_handle_is_used(lh) ) failed |
| Comments |
| Comment by Gerrit Updater [ 23/Oct/20 ] |
|
Mike Pershin (mpershin@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/40382 |
| Comment by Gerrit Updater [ 03/Nov/20 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/40382/ |
| Comment by Peter Jones [ 03/Nov/20 ] |
|
Landed for 2.14 |