gh-Mbed-TLS/TF-PSA-Crypto
Watch
1
0
Fork
You've already forked TF-PSA-Crypto
 0
Code Issues 167 Pull requests 92 Releases 5 Activity

Fix PSA lifetime persistence argument #731

Open
parmi93 wants to merge 2 commits from parmi93/patch-2 into development
pull from: parmi93/patch-2
merge into: gh-Mbed-TLS:development
Conversation 2 Commits 2 Files changed 1 +1 -1
parmi93 commented 2026-03-30 04:34:19 -05:00 (Migrated from github.com)

Pass PSA_KEY_PERSISTENCE_DEFAULT to PSA_KEY_LIFETIME_FROM_PERSISTENCE_AND_LOCATION() instead of PSA_KEY_LIFETIME_PERSISTENT. The macro expects a psa_key_persistence_t, but the previous code incorrectly passed a value already representing a constructed lifetime. This aligns the call with the API specification and ensures correct lifetime construction.

Pass `PSA_KEY_PERSISTENCE_DEFAULT` to `PSA_KEY_LIFETIME_FROM_PERSISTENCE_AND_LOCATION()` instead of `PSA_KEY_LIFETIME_PERSISTENT`. The macro expects a `psa_key_persistence_t`, but the previous code incorrectly passed a value already representing a constructed lifetime. This aligns the call with the API specification and ensures correct lifetime construction.
bjwtaylor commented 2026-04-30 07:28:07 -05:00 (Migrated from github.com)

Hi @parmi93, many thanks for submitting this. It looks like the branch on you fork is based of a fairly old commit form tf-psa-crypto. Are you able to update the fork and rebase, as I think the current CI issue is unrelated to your changes and should disappear if you pull in the relevant changes.

Hi @parmi93, many thanks for submitting this. It looks like the branch on you fork is based of a fairly old commit form tf-psa-crypto. Are you able to update the fork and rebase, as I think the current CI issue is unrelated to your changes and should disappear if you pull in the relevant changes.
parmi93 commented 2026-04-30 14:52:44 -05:00 (Migrated from github.com)

Hi @bjwtaylor I merged the upstream development branch into my branch (patch-2).

Hi @bjwtaylor I merged the upstream `development` branch into my branch (`patch-2`).
This pull request is broken due to missing fork information.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 'parmi93/patch-2:parmi93/patch-2'
git switch 'parmi93/patch-2'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'development'
git merge --no-ff 'parmi93/patch-2'
git switch 'parmi93/patch-2'
git rebase 'development'
git switch 'development'
git merge --ff-only 'parmi93/patch-2'
git switch 'parmi93/patch-2'
git rebase 'development'
git switch 'development'
git merge --no-ff 'parmi93/patch-2'
git switch 'development'
git merge --squash 'parmi93/patch-2'
git switch 'development'
git merge --ff-only 'parmi93/patch-2'
git switch 'development'
git merge 'parmi93/patch-2'
git push origin 'development'
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
api-break
This issue/PR breaks the API and must wait for a new major version

  
approved
Design and code approved - may be waiting for CI or backports

  
bug
Something isn't working

  
component-docs
Docs / website issues filed here for tracking

  
component-platform
Portability layer and build scripts

  
component-test
Test framework and CI scripts

  
dependencies
Pull requests that update a dependency file

  
deprecation
needs deprecation announcement

  
DO-NOT-MERGE

   
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
This issue is not being actively worked on, but PRs welcome.

  
needs-adoption
stalled PR that someone should pick up and complete

  
needs-backports
Backports are missing or are pending review and approval.

  
needs-ci
Needs to pass CI tests

  
needs-design-approval
Needs design discussion / approval

  
needs-info
An issue or PR which needs further info from the reporter / author

  
needs-preceding-pr
Requires another PR to be merged first

  
needs-review
Every commit must be reviewed by at least two team members

  
needs-reviewer
This PR needs someone to pick it up for review

  
needs-work

   
priority-high
High priority - will be reviewed soon

  
priority-low
Low priority - this may not receive review soon

  
priority-medium
Medium priority - this can be reviewed as time permits

  
priority-scheduled
This PR is big - it will require time to be scheduled for review

  
priority-very-high
Highest priority - prioritise this over other review work

  
resolved-after-1.1
The issue is resolved in development, but still present in 1.1 LTS.

  
single-reviewer
This PR qualifies for having only one reviewer

  
size-l
Estimated task size: large (2w+)

  
size-m
Estimated task size: medium (~1w)

  
size-optimisation

   
size-s
Estimated task size: small (~2d)

  
size-xs
Estimated task size: extra small (a few hours at most)

No labels
api-break
approved
bug
component-docs
component-platform
component-test
dependencies
deprecation
DO-NOT-MERGE
enhancement
good first issue
help wanted
needs-adoption
needs-backports
needs-ci
needs-design-approval
needs-info
needs-preceding-pr
needs-review
needs-reviewer
needs-work
priority-high
priority-low
priority-medium
priority-scheduled
priority-very-high
resolved-after-1.1
single-reviewer
size-l
size-m
size-optimisation
size-s
size-xs
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
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/TF-PSA-Crypto!731
No description provided.