Support MBEDTLS_THREADING_ALT in the mutex usage verification framework #207

New issue

Open

opened 2025-09-05 04:24:16 -05:00 by gilles-peskine-arm · 0 comments

gilles-peskine-arm commented

2025-09-05 04:24:16 -05:00

(Migrated from github.com)

The mutex usage verification framework should work with MBEDTLS_THREADING_ALT, because it's part of how a platform integrator can test that their threading abstraction matches our requirements.

This issue spans both the framework repository and the consuming repository(ies). At least in TF-PSA-Crypto, and ideally in 3.6 as well, have an all.sh component that runs with MBEDTLS_THREADING_ALT, with the mutex usage verification framework enabled.

Closely related: https://github.com/Mbed-TLS/mbedtls-framework/issues/206. I'm not sure if it makes more sense to do 206 before 207, 207 before 206, or both together.

The mutex usage verification framework should work with `MBEDTLS_THREADING_ALT`, because it's part of how a platform integrator can test that their threading abstraction matches our requirements. This issue spans both the framework repository and the consuming repository(ies). At least in TF-PSA-Crypto, and ideally in 3.6 as well, have an `all.sh` component that runs with `MBEDTLS_THREADING_ALT`, with the mutex usage verification framework enabled. Closely related: https://github.com/Mbed-TLS/mbedtls-framework/issues/206. I'm not sure if it makes more sense to do 206 before 207, 207 before 206, or both together.

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gh-Mbed-TLS/mbedtls-framework#207

No description provided.

Rows
Columns