diff options
| author | Dylan Reid <dgreid@chromium.org> | 2017-06-20 10:15:51 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2017-06-27 00:20:33 -0700 |
| commit | 0584fe9fb2694fad6dc841a8215e8017c18b19c7 (patch) | |
| tree | 0180ba9aaec5211b367b2656775a82dac2fe736f /data_model | |
| parent | 045c7133dd22e4cc5fe62af136c15b04a8b8a485 (diff) | |
| download | crosvm-0584fe9fb2694fad6dc841a8215e8017c18b19c7.tar crosvm-0584fe9fb2694fad6dc841a8215e8017c18b19c7.tar.gz crosvm-0584fe9fb2694fad6dc841a8215e8017c18b19c7.tar.bz2 crosvm-0584fe9fb2694fad6dc841a8215e8017c18b19c7.tar.lz crosvm-0584fe9fb2694fad6dc841a8215e8017c18b19c7.tar.xz crosvm-0584fe9fb2694fad6dc841a8215e8017c18b19c7.tar.zst crosvm-0584fe9fb2694fad6dc841a8215e8017c18b19c7.zip | |
Limit types that can be read from guest memory
Not all types are safe to read from guest memory. Any type with a reference or pointer will be initialized to random bits that don't refer to a valid address. This can cause dangling pointer and general unsafe behavior. To fix this, limit types that can be read with read_obj to those that implement the unsafe trait `DataInit`. Provide implementations of `DataInit` for intrinsic types that are obviously safe to initialize with random data. Implement the needed traits for bootparam types as they are read from the kernel image directly. Change-Id: I1040f5bc1b2fc4c58c87d8a2ce3f618edcf6f9b1 Signed-off-by: Dylan Reid <dgreid@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/540750 Reviewed-by: Zach Reizner <zachr@chromium.org>
Diffstat (limited to 'data_model')
0 files changed, 0 insertions, 0 deletions