[LU-17021] ksnr_max_conns is used before it is set Created: 08/Aug/23 Updated: 06/Feb/24 Resolved: 19/Aug/23 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.16.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Cyril Bordage | Assignee: | Cyril Bordage |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Severity: | 3 | ||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
In ksocknal_add_peer, ksnr_max_conns is set but only after it is used in ksocknal_associate_cb_conn_locked called from ksocknal_add_conn_cb_locked. It seems it could lead to bad ksnr_connected value. |
| Comments |
| Comment by Gerrit Updater [ 08/Aug/23 ] |
|
"Cyril Bordage <cbordage@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/51890 |
| Comment by Gerrit Updater [ 19/Aug/23 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/51890/ |
| Comment by Peter Jones [ 19/Aug/23 ] |
|
Landed for 2.16 |