Skip to content

Move everest headers #153

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

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

bjwtaylor
Copy link

@bjwtaylor bjwtaylor commented Apr 2, 2025

Description

Move everest headers

PR checklist

@bjwtaylor bjwtaylor force-pushed the move-everest-headers branch 2 times, most recently from d6bf105 to b388233 Compare April 2, 2025 08:41
@bjwtaylor bjwtaylor added 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 labels Apr 8, 2025
@felixc-arm felixc-arm self-requested a review April 15, 2025 10:02
@@ -172,7 +172,8 @@ def main():
parser.add_argument('--include', '-I',
action='append', default=['tf-psa-crypto/include',
'tf-psa-crypto/drivers/builtin/include',
'tf-psa-crypto/drivers/everest/include',
'tf-psa-crypto/drivers/everest/include/',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Has this change accidentally been split on to two lines? I assume it's meant to be tf-psa-crypto/drivers/everest/include/tf-psa-crypto/private rather than two separate elements in the list.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It just looks like a typo, I've removed it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I need to remember that these reviews never show any lines under the one you click... anyway now in scripts/test_psa_constant_names.py there's + 'tf-psa-crypto/private/', which is a directory that doesn't exist...

I still think that this change should be replacing 'tf-psa-crypto/drivers/everest/include', with tf-psa-crypto/drivers/everest/include/tf-psa-crypto/private but as it's a long line perhaps

'tf-psa-crypto/drivers/everest/include/'
'tf-psa-crypto/private',

works I believe, which is how it was in the original version of this PR, just with the comma removed after /include/' so that it doesn't create a new list element and instead concatenates 'tf-psa-crypto/private' at the end of everest/include/ which I think was the intended result of this change originally?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've updated it, lets see if the ci passes.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you just missed the / after include (or before the second tf-psa-crypto) in the updated patch - although I don't think the CI will pass here anyway as it's using the development mbedtls & tf-psa-crypto so naturally can't find anything in tf-psa-crypto/drivers/everest/include/tf-psa-crypto/private as the directory doesn't exist.

I this issue (the directory doesn't exist in development) is causing both the CI issues (i.e. the check_names issue and the compilation issue where it tries to include drivers/everest/include/tf-psa-crypto/private/ from the change in psa_stoage.py) - so presumably we would want this patch changed to accommodate both scenarios (everest headers are in drivers/everest/include or drivers/everest/include/tf-psa-crypto/private) and then can remove the old functionality in a later patch...

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a duplicate @gilles-peskine-arm comment. Basically we will need both the 3.6 paths and the new path present or the CI will fail with the older version. I'll resolve the one below and hopefully that will resolve both.

@bjwtaylor bjwtaylor force-pushed the move-everest-headers branch from 42cf70d to 1ef13c8 Compare April 22, 2025 08:31
Ben Taylor added 4 commits April 22, 2025 09:44
@gilles-peskine-arm gilles-peskine-arm self-requested a review April 24, 2025 09:32
@gilles-peskine-arm gilles-peskine-arm added priority-high High priority - will be reviewed soon and removed needs-reviewer This PR needs someone to pick it up for review labels Apr 24, 2025
Copy link
Contributor

@gilles-peskine-arm gilles-peskine-arm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This breaks (or apparently just removes some checks from) 3.6.

@@ -703,8 +703,8 @@ def comprehensive_parse(self):
"include/tf-psa-crypto/*.h",
"include/mbedtls/*.h",
"drivers/builtin/include/mbedtls/*.h",
"drivers/everest/include/everest/everest.h",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the framework, we need to keep the old paths everywhere, since they're still relevant for 3.6. It doesn't matter if some of these patterns match nothing in a given branch (except for human readers who might not think of the LTS branches, for which a comment could be helpful).

@@ -172,7 +172,8 @@ def main():
parser.add_argument('--include', '-I',
action='append', default=['tf-psa-crypto/include',
'tf-psa-crypto/drivers/builtin/include',
'tf-psa-crypto/drivers/everest/include',
'tf-psa-crypto/drivers/everest/include'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
'tf-psa-crypto/drivers/everest/include'
'tf-psa-crypto/drivers/everest/include,'

@gilles-peskine-arm gilles-peskine-arm added needs-work and removed needs-review Every commit must be reviewed by at least two team members, labels Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-work priority-high High priority - will be reviewed soon
Projects
Development

Successfully merging this pull request may close these issues.

3 participants