You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a follow-up of #1424.
PR #1450, which fixed #1424, did not update the session id allocation process accordingly.
Because from #1450rsp_session_id occupies the most-significant bytes of a whole session_id,
thus the req_session_id inside libspdm_allocate_req_session_id() should be caululated from 0xFFFF,
and rsp_session_id inside libspdm_allocate_rsp_session_id() should be caululated from 0xFFFF0000.
This is a follow-up of #1424.
PR #1450, which fixed #1424, did not update the session id allocation process accordingly.
Because from #1450 rsp_session_id occupies the most-significant bytes of a whole session_id,
thus the req_session_id inside
libspdm_allocate_req_session_id()
should be caululated from 0xFFFF,and rsp_session_id inside
libspdm_allocate_rsp_session_id()
should be caululated from 0xFFFF0000.libspdm/library/spdm_requester_lib/libspdm_req_common.c
Lines 9 to 25 in bda8d7e
libspdm/library/spdm_responder_lib/libspdm_rsp_common.c
Lines 9 to 25 in bda8d7e
The text was updated successfully, but these errors were encountered: