Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 2.12.0, Lustre 2.13.0
-
None
-
3
-
9223372036854775807
Description
ll_update_lsm_md() down_write() if lli->lli_lsm_md is NULL, and tries to initialize it, but if a concurrent lookup initialized lli->lli_lsm_md after this check and before taking write lock, it will up_read(), so the write lock is not released, therefore subsequent lookup will deadlock on this.
Attachments
Issue Links
- is related to
-
LU-13099 ll_set_inode()) Can not initialize inode warning
-
- Resolved
-
Activity
Link | New: This issue is related to DDN-1041 [ DDN-1041 ] |
Link | Original: This issue is related to JFC-17 [ JFC-17 ] |
Link | Original: This issue is related to JFC-27 [ JFC-27 ] |
Link | New: This issue is related to JFC-20 [ JFC-20 ] |
Labels | Original: LTS12 |
Fix Version/s | New: Lustre 2.12.4 [ 14690 ] |
Fix Version/s | New: Lustre 2.14.0 [ 14490 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/37325/
Subject:
LU-13121llite: fix deadlock in ll_update_lsm_md()Project: fs/lustre-release
Branch: b2_12
Current Patch Set:
Commit: ed1391adec4a10075a72b21c506293c6cf9ece95