[LU-11424] incorrect amount of cpts copied to lnet_cpts Created: 25/Sep/18 Updated: 23/Feb/21 Resolved: 06/Oct/18 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.11.0, Lustre 2.12.0, Lustre 2.10.5 |
| Fix Version/s: | Lustre 2.12.0, Lustre 2.10.6 |
| Type: | Bug | Priority: | Critical |
| Reporter: | James A Simmons | Assignee: | James A Simmons |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Any LNet setup |
||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
While porting the Multi-Rail work to the linux lustre client a bug exposed itself that is in the OpenSFS branch but yet has not shown up yet. The wrong size is used to copy the cpts to net_cpts which causes the follow crash: RIP: 0010:lnet_match2mt.isra.8+0x2b/0x40 [lnet] |
| Comments |
| Comment by Gerrit Updater [ 25/Sep/18 ] |
|
James Simmons (uja.ornl@yahoo.com) uploaded a new patch: https://review.whamcloud.com/33229 |
| Comment by Gerrit Updater [ 05/Oct/18 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/33229/ |
| Comment by Gerrit Updater [ 06/Oct/18 ] |
|
Minh Diep (mdiep@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/33312 |
| Comment by Gerrit Updater [ 22/Nov/18 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/33312/ |
| Comment by Alexander Boyko [ 10/Jan/19 ] |
|
I think there is some more memcpy errors. 8cbb8cd3 (Amir Shehata 2015-12-11 20:02:54 -0800 204) 8cbb8cd3 (Amir Shehata 2015-12-11 20:02:54 -0800 205) memcpy(array, net->net_cpts, net->net_ncpts); 8cbb8cd3 (Amir Shehata 2015-12-11 20:02:54 -0800 206) loc = array + net->net_ncpts; 8cbb8cd3 (Amir Shehata 2015-12-11 20:02:54 -0800 207) memcpy(loc, added_cpts, j); |
| Comment by Gerrit Updater [ 31/Oct/19 ] |
|
|
| Comment by Andreas Dilger [ 12/Feb/20 ] |
|
This issue was closed for the 2.12.0 release. Adding new patches in a later release makes it harder to track the new patch and where it needs to be fixed. I've moved the patch over to |