[LU-13708] lnet_notify can set route aliveness incorrectly Created: 23/Jun/20 Updated: 22/Aug/22 Resolved: 11/Mar/21 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.15.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Chris Horn | Assignee: | Chris Horn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
lnet_notify() modifies route aliveness in two ways: In both cases, the aliveness value assigned is determined by a call In general, we should not set lp_alive based on an lnet_notify() An exception to the above exists when the reset argument to |
| Comments |
| Comment by Gerrit Updater [ 23/Jun/20 ] |
|
Chris Horn (chris.horn@hpe.com) uploaded a new patch: https://review.whamcloud.com/39160 |
| Comment by Gerrit Updater [ 10/Mar/21 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/39160/ |
| Comment by Peter Jones [ 11/Mar/21 ] |
|
Landed for 2.15 |