diff options
| author | David Horstmann <david.horstmann@arm.com> | 2024-03-18 15:51:03 +0000 |
|---|---|---|
| committer | David Horstmann <david.horstmann@arm.com> | 2024-03-18 15:51:03 +0000 |
| commit | 0ea8071bda38999ff59d60ca063898efaf11d1c3 (patch) | |
| tree | ceb87765493355d2f8d8336541aff8ec5b99761b | |
| parent | 4d01066311b378c8044595e2023cc39aeb7b45b0 (diff) | |
| download | mbedtls-0ea8071bda38999ff59d60ca063898efaf11d1c3.tar.gz | |
Remove 'Question' line around testing
This question has been resolved, as we know that we can test
transparently.
Signed-off-by: David Horstmann <david.horstmann@arm.com>
| -rw-r--r-- | docs/architecture/psa-shared-memory.md | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/docs/architecture/psa-shared-memory.md b/docs/architecture/psa-shared-memory.md index 7622329c5..b8e0cd372 100644 --- a/docs/architecture/psa-shared-memory.md +++ b/docs/architecture/psa-shared-memory.md @@ -341,8 +341,6 @@ It should be possible to work around this by manually rounding buffer lengths up **Design decision: Implement memory poisoning tests with both Valgrind's memcheck and ASan manual poisoning.** -**Question: Should we try to build memory poisoning validation on existing Mbed TLS tests, or write new tests for this?** - ##### Validation with new tests Validation with newly created tests would be simpler to implement than using existing tests, since the tests can be written to take into account memory poisoning. It is also possible to build such a testsuite using existing tests as a starting point - `mbedtls_test_psa_exercise_key` is a test helper that already exercises many PSA operations on a key. This would need to be extended to cover operations without keys (e.g. hashes) and multipart operations, but it provides a good base from which to build all of the required testing. |