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

unused symbols in oak_restricted_kernel #4783

Open
tiziano88 opened this issue Feb 9, 2024 · 0 comments
Open

unused symbols in oak_restricted_kernel #4783

tiziano88 opened this issue Feb 9, 2024 · 0 comments
Assignees

Comments

@tiziano88
Copy link
Collaborator

❯ cargo check
    Checking oak_functions_service v0.1.0 (/home/tzn/src/oak/oak_functions_service)
warning: unused import: `Stage0DiceData`
  --> oak_restricted_kernel/src/syscall/dice_data.rs:19:52
   |
19 | use oak_dice::evidence::{RestrictedKernelDiceData, Stage0DiceData};
   |                                                    ^^^^^^^^^^^^^^
   |
   = note: `#[warn(unused_imports)]` on by default

warning: unused variable: `buf`
  --> oak_restricted_kernel/src/syscall/dice_data.rs:87:25
   |
87 |     fn write(&mut self, buf: &[u8]) -> Result<isize, oak_restricted_kernel_interface::Errno> {
   |                         ^^^ help: if this is intentional, prefix it with an underscore: `_buf`
   |
   = note: `#[warn(unused_variables)]` on by default

warning: struct `WriteState` is never constructed
  --> oak_restricted_kernel/src/syscall/dice_data.rs:50:8
   |
50 | struct WriteState {
   |        ^^^^^^^^^^
   |
   = note: `#[warn(dead_code)]` on by default

warning: `oak_restricted_kernel` (lib) generated 3 warnings (run `cargo fix --lib -p oak_restricted_kernel` to apply 2 suggestions)
    Checking oak_functions_containers_app v0.1.0 (/home/tzn/src/oak/oak_functions_containers_app)
    Checking oak_functions_enclave_service v0.1.0 (/home/tzn/src/oak/oak_functions_enclave_service)
    Finished dev [unoptimized + debuginfo] target(s) in 0.58s

@jul-sh I haven't looked closely, but this sounds related to some of your changes? if not, could you re-assign to who may know more about it?

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

No branches or pull requests

2 participants