[LU-12264] The lnet peer discovery queue (lnet_peer.lp_dc_pendq) is susceptible to concurrent manipulation Created: 02/May/19 Updated: 08/Oct/19 Resolved: 26/Jul/19 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.13.0, Lustre 2.12.2 |
| Fix Version/s: | Lustre 2.13.0, Lustre 2.12.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Chris Horn | Assignee: | Chris Horn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
This issue was discovered while testing the MR routing feature, but the bug exists in, at least, master and b2_12 as well. On an initial call to lnet_select_pathway(), messages are added to a peer's discovery queue only under protection of lnet_net_lock_current(). If two threads are sending to the same peer, but that peer is pending discovery, and the two threads are on different CPTs, then it is possible for them to perform the list add at the same time. This can result in corruption of the list. |
| Comments |
| Comment by Gerrit Updater [ 02/May/19 ] |
|
Chris Horn (hornc@cray.com) uploaded a new patch: https://review.whamcloud.com/34798 |
| Comment by Gerrit Updater [ 07/Jun/19 ] |
|
Amir Shehata (ashehata@whamcloud.com) merged in patch https://review.whamcloud.com/34798/ |
| Comment by Gerrit Updater [ 03/Sep/19 ] |
|
Minh Diep (mdiep@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/36037 |
| Comment by Gerrit Updater [ 04/Oct/19 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/36037/ |