[LU-5639] Message is hashed to invalid match-table of LNet request portal

Duplicate — Sat, 6 Oct 2018 14:34:05 +0000

When new message arrived at LNet request portal, if there is no receiving buffer (ME/MD) in match-table of the partition that message arrived in, either because service does not post any buffer in that partition, or because server is under memory pressure, LNet will increase a integer (rotor) then hash this message to another match-table within a different partition which has receiving buffers. This rotor should be unsigned when hashing, otherwise we will refer to illegal address when the integer is overflowed.

This issue should be rare because Lustre services will always post enough request buffers

Whamcloud Community JIRA

[LU-5639] Message is hashed to invalid match-table of LNet request portal