Repository navigation
libmctp: reassembly timeout and TO-bit issues #124456
Unanswered
YuvalYeruham2
asked this question in
General
Replies: 2 comments
|
Please submit the proposed fix to https://gerrit.openbmc.org/q/project:openbmc/libmctp - we can get it from there. About backporting to 4.5, I think it could be done if an issue is opened, but I'll let @teburd comment on that. |
0 replies
|
Thanks for the guidance. I've pushed the fix to Gerrit as a series of 4 commits:
I'm new to the OpenBMC review process, so any help getting these reviewed and merged would be much appreciated, for example pointing me to the right reviewers or maintainers. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We're implementing MCTP over SMBus on Zephyr 4.5.0, which uses libmctp b6be45d . We found two message reassembly issues in libmctp's core.c and reported them upstream in openbmc/libmctp, along with a proposed fix: openbmc/libmctp#27
In short:
Both are also present in Zephyr's libmctp fork.
Once a fix lands in openbmc/libmctp, would the fork be synced, and could the update be backported to Zephyr 4.5.x?
@teburd @edersondisouza
All reactions