minkipc: add patch for pkcs11 static initialization issue#2739
minkipc: add patch for pkcs11 static initialization issue#2739Jiaxing Li (jiaxli-QC) wants to merge 1 commit into
Conversation
Test Results 110 files + 89 652 suites +631 9h 34m 59s ⏱️ + 8h 39m 32s For more details on these failures, see this check. Results for commit f98f934. ± Comparison against base commit 2be91de. This pull request removes 4 and adds 152 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
|
Why are we having this PR which is duplicating #2726 and ignoring the review comments which were already made there? |
Hi Ricardo Salveti (@ricardosalveti) , I checked with the original PR owner, they informed me that they are unable to validate the PR due to environment setup issues on their Linux machine. Hence, they've closed that PR and asked Jiaxing Li (@jiaxli-QC) to take over. Jiaxing Li (@jiaxli-QC) can you please take care of the comments provided on the other PR and ensure we are aligned with the expectations here? |
| Modified the compound literals used for session object templates to avoid problems arising from taking the address of a compound literal during | ||
| static initialization. | ||
|
|
||
| Upstream-Status: Inappropriate [tests applicable for optee] |
There was a problem hiding this comment.
This Upstream-Status is wrong, please mention the status as 'Submitted/Merged' and explain that this patch for back-porting the fix to our v4.0.0 tag of optee-test.
There was a problem hiding this comment.
commit: 75f4e20
Updated.
- For Upstream-Status item, set the status as
Backport [https://github.com/OP-TEE/optee_test/pull/821/changes/9dd9d864042871518a257af3a46f53dc299ae778].
Please refer to guidance: https://docs.yoctoproject.org/dev/contributor-guide/recipe-style-guide.html#patch-upstream-status - Add the context in commit message
a64f430 to
75f4e20
Compare
Yes, Updated. Please review. All test cases for PKCS#11 passed on PURWA. |
Which issue? The issue is mentioned in PR description but not the commit message. |
I think that I have described the issue in the second paragraph of the commit message and explained why we need this patch. Please review it.
|
|
Start by describing the issue. |
meta-qcom uses OP-TEE optee_test v4.0.0, where pkcs11 test code takes
the address of a compound literal in a static initializer (e.g.
&(CK_BBOOL){CK_TRUE}). Under compiler optimization, the storage for such
compound literals may be reused or overlap with other objects, which can
result in invalid values being read back during the test.
Add a new patch (0003) to the minkipc recipe's optee_test source to fix
this issue, and reference it in SRC_URI. The patch replaces the compound
literal usage with statically allocated objects to ensure correct
initialization and improve reliability.
Backport of OP-TEE/optee_test@31fa5e6.
Signed-off-by: Jiaxing Li <jiaxing.li@oss.qualcomm.com>
75f4e20 to
f98f934
Compare
|
Update commit message. |
meta-qcom uses OP-TEE optee_test v4.0.0, where pkcs11 test code takes the address of a compound literal in a static initializer (e.g. &(CK_BBOOL){CK_TRUE}). Under compiler optimization, the storage for such compound literals may be reused or overlap with other objects, which can result in invalid values being read back during the test.
Add a new patch (0003) to the minkipc recipe's optee_test source to fix this issue, and reference it in SRC_URI. The patch replaces the compound literal usage with statically allocated objects to ensure correct initialization and improve reliability.
Inherited from: #2726