Skip to content
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

Make use of the User0 permission? #371

Open
rmn30 opened this issue Dec 9, 2024 · 1 comment
Open

Make use of the User0 permission? #371

rmn30 opened this issue Dec 9, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@rmn30
Copy link
Collaborator

rmn30 commented Dec 9, 2024

I just noticed a comment in token_key_new that the User0 permission is reserved for possible future use by the allocator so is cleared on SKeys at the moment. I only noticed because I'm using an SKey as a handy sealing type capability in the ISA test and it slightly reduces the coverage of the candperms test. It's not a big deal but just noting it here for future reference and to discuss possible uses.

@rmn30 rmn30 added the enhancement New feature or request label Dec 9, 2024
@rmn30
Copy link
Collaborator Author

rmn30 commented Dec 9, 2024

Notes on this:

  1. SObj allocation and sealing are combined at the moment. This makes sense because we have to know we're allocating a sealed object so we reserve space for the metadata. However, it means there's no token_seal function so it doesn't really make sense to have separate 'allocate' permission in the SKey.
  2. If you can unseal an SObj then (I think) you can free it at current so a separate deallocate permission is only useful for delegating the ability to deallocate without the ability to unseal. This does sound potentially useful as it potentially avoids a call into the owning compartment for deallocation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant