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.

Sign up for GitHub

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

Jump to bottom

Allocator service triggers EINVAL error in dmesg #397

Open

sabin-rapan opened this issue Jul 27, 2022 · 0 comments

Labels

good first issue

Contributor

sabin-rapan commented Jul 27, 2022 •

edited

Loading

This piece of code https://github.com/aws/aws-nitro-enclaves-cli/blame/main/bootstrap/nitro-enclaves-allocator#L129-L138 is called every time the allocator service is started.

It writes an empty string to /sys/module/nitro_enclaves/parameters/ne_cpus. The driver however doesn't know how to interpret this empty string (see https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/virt/nitro_enclaves/ne_misc_dev.c#n431) so it tries to allocate this invalid cpu pool, fails, then prints EINVAL to dmesg.

Everything works perfectly fine however, so no actual issue just that seeing errors in dmesg is super confusing when debugging other stuff.

Edit: this is not an issue with nitro-cli, just with the driver.

sabin-rapan added the good first issue label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment