Skip to content

mctp-estack: Consider MCTP transport header separately from the mtu#52

Open
SafetyInObscurity wants to merge 1 commit into
CodeConstruct:mainfrom
SafetyInObscurity:mtu
Open

mctp-estack: Consider MCTP transport header separately from the mtu#52
SafetyInObscurity wants to merge 1 commit into
CodeConstruct:mainfrom
SafetyInObscurity:mtu

Conversation

@SafetyInObscurity
Copy link
Copy Markdown
Contributor

The minimum payload for a non-eom MCTP packet is 64 bytes. Currently the Fragmenter considers MCTP transport headers as part of the mtu. This means the minimum mtu creates packets with 60 bytes of payload, less than the minimum. To fix this, the mtu now sets the maximum payload bytes, and the header is prepended.

All packets returned by the fragmenter will now be four bytes longer. This needs to be accommodated by the size of input buffers and the expected length of packets.

@SafetyInObscurity SafetyInObscurity changed the title mctp-estack: Consider MCTP transport header separately from the mtu i… mctp-estack: Consider MCTP transport header separately from the mtu May 21, 2026
@SafetyInObscurity SafetyInObscurity force-pushed the mtu branch 9 times, most recently from ed50a51 to 19c75f3 Compare May 21, 2026 08:12
…n the Fragmenter

The minimum payload for a non-eom MCTP packet is 64 bytes.
Currently the Fragmenter considers MCTP transport headers as part of the mtu.
This means the minimum mtu creates packets with 60 bytes of payload, less than the minimum.
To fix this, the mtu now sets the maximum payload bytes, and the header is prepended.
All packets returned by the fragmenter will now be four bytes longer.
This needs to be accommodated by the size of input buffers and the expected length of packets.

Signed-off-by: James Lee <james@codeconstruct.com.au>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant