Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

port: fix memory leak in SHA256 #748

Merged
merged 1 commit into from
Feb 18, 2025
Merged

port: fix memory leak in SHA256 #748

merged 1 commit into from
Feb 18, 2025

Conversation

sam-golioth
Copy link
Contributor

mbedtls_sha256_free() does not free memory, it only zeroes out the SHA context struct.

`mbedtls_sha256_free()` does not free memory, it only zeroes out
the SHA context struct.

Signed-off-by: Sam Friedman <[email protected]>
@sam-golioth sam-golioth self-assigned this Feb 14, 2025
Copy link

Visit the preview URL for this PR (updated for commit cc5d1b9):

https://golioth-firmware-sdk-doxygen-dev--pr748-sha-memory-lea-51foeh1b.web.app

(expires Fri, 21 Feb 2025 21:13:16 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: a9993e61697a3983f3479e468bcb0b616f9a0578

@sam-golioth sam-golioth marked this pull request as ready for review February 15, 2025 00:46
Copy link

Code Coverage

Code Coverage

Package Line Rate Branch Rate Health
include.golioth 75% 50%
port.linux 62% 34%
port.utils 58% 46%
port.zephyr 53% 22%
src 67% 30%
Summary 66% (2717 / 4118) 30% (1123 / 3736)

Copy link

codecov bot commented Feb 18, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Files with missing lines Coverage Δ
port/zephyr/golioth_sys_zephyr.c 72.53% <100.00%> (+1.00%) ⬆️

... and 3 files with indirect coverage changes

@sam-golioth sam-golioth merged commit 5dd321b into main Feb 18, 2025
139 of 140 checks passed
@sam-golioth sam-golioth deleted the sha_memory_leak branch February 18, 2025 13:22
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.

4 participants