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

Runtime manager segfaults #544

Open
gbryant-arm opened this issue Oct 13, 2022 · 0 comments
Open

Runtime manager segfaults #544

gbryant-arm opened this issue Oct 13, 2022 · 0 comments
Labels
bug Something isn't working trusted-veracruz-runtime Something related to the trusted Veracruz runtime

Comments

@gbryant-arm
Copy link
Contributor

gbryant-arm commented Oct 13, 2022

Describe the bug
The runtime manager segfaults after some time repeatedly opening and closing TLS connections with Veracruz-Client.
This bug can be reproduced on Nitro and Linux.
Error message on Nitro:

[ 1975.584292] runtime_manager[594]: segfault at 9 ip 0000000000a6714d sp 00007ffde3018228 error 4 in runtime_manager_enclave[400000+1b3c000]

It seems to be caused by a memory leak in the runtime manager.

To Reproduce

  • Deploy Veracruz (run PAS, server, runtime manager)
  • Provision the same file in a loop:
    for((i=0;i<100000;i++)); do
    echo $i;
    $client_path policy.json \
        --data /input/file=file \
        --identity data_client_cert.pem \
        --key data_client_key.pem
    done
    
  • Wait until the runtime manager segfaults

Expected behaviour
The runtime manager should be able to handle an infinite amount of successive TLS connections

@gbryant-arm gbryant-arm added bug Something isn't working trusted-veracruz-runtime Something related to the trusted Veracruz runtime labels Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working trusted-veracruz-runtime Something related to the trusted Veracruz runtime
Projects
None yet
Development

No branches or pull requests

1 participant