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

Reading uninitialized memory from FUSE #1260

Open
mkroening opened this issue Jun 6, 2024 · 0 comments
Open

Reading uninitialized memory from FUSE #1260

mkroening opened this issue Jun 6, 2024 · 0 comments
Assignees

Comments

@mkroening
Copy link
Member

mkroening commented Jun 6, 2024

#1248 has mare it mode likely that we end up reading uninitialized memory for FUSE. I suspect this is coming from subtle codegen changes (aka we are doing something wrong with uninit memory or references).

$ cargo xtask ci qemu --arch x86_64 --profile release --package rftrace-example --virtiofsd
...
Saving traces to disk...!
0xc1b000, Events { ptr: 0xc1b000, len: 2000, cap: 2000 }
  Parsing TID 1...!
  Writing to disk: 8 events, 128 bytes (/root/tracedir/1.dat)
  Parsed all events!
Creating fake uftrace data dir at /root/tracedir..
  Creating ./info
    feats = TASK_SESSION | SYM_REL_ADDR
    info = CMDLINE | TASKINFO
    cmdline = 'fakeuftrace'
    tid = [1]
  Creating ./task.txt
[0][PANIC] panicked at src/fs/fuse.rs:479:47:
called `Result::unwrap()` on an `Err` value: TryFromIntError(())

This happens while converting a u64 into an i64, so this is most definitely not a real value.

st_blocks: attr.blocks.try_into().unwrap(),

I'll disable the test in CI for now.

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