[LU-6176] no crash for unknown incoming lnet message type Created: 29/Jan/15 Updated: 16/Mar/16 Resolved: 16/Mar/16 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.7.0, Lustre 2.5.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Liang Zhen (Inactive) | Assignee: | Liang Zhen (Inactive) |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 17277 |
| Description |
|
LNet will crash for unknown incoming message type, this is bad and will prevent any change to lnet message protocol. |
| Comments |
| Comment by Andreas Dilger [ 02/Feb/15 ] |
|
Liang, are you planning to work on this for 2.7.0? |
| Comment by Liang Zhen (Inactive) [ 03/Feb/15 ] |
|
yes, this should be a simple patch, I will work it out soon. |
| Comment by Liang Zhen (Inactive) [ 03/Feb/15 ] |
|
sorry I was wrong, lnet_parse() will not LBUG on unknown message type, lnet_parse has two places that check message type, at the begin of lnet_parse, it returns EPROTO for unknown message type, there is another code block which LBUG for unknown message type, but it should never happen. So I think we can close this ticket. |
| Comment by Joseph Gmitter (Inactive) [ 16/Mar/16 ] |
|
Need to reopen/resolve again to fix the Resolution status to be "Not a bug". |