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

fuzz_nvme_driver: fix fuzzer-found bugs #585

Merged
merged 5 commits into from
Jan 8, 2025

Conversation

mattkur
Copy link
Contributor

@mattkur mattkur commented Dec 22, 2024

Fix some issues in the NvmeDriver fuzzer:

  • Sanitize the input provided to .read, .write, and .flush to avoid contract violations (NvmeDriver is an interface interal to NvmeDisk, and it's not useful for the fuzzer to find cases where NvmeDriver enforces the contract).
  • Fuzzer can handle when .read, .write, .flush return an Error (bad input can fail an IO; this is fine).
  • Graceful check for some bad device behavior, rathern than just crash. This will change behavior of the NvmeDriver in prod, but if we see a bad device we will still see key errors in our logs.

* Sanitize the input provided to .read, .write, and .flush
  to avoid contract violations (`NvmeDriver` is an interface
  interal to `NvmeDisk`, and it's not useful for the fuzzer
  to find cases where `NvmeDriver` enforces the contract).
* Fuzzer can handle when .read, .write, .flush return an
  Error (bad input can fail an IO; this is fine).
* Graceful check for some bad device behavior, rathern than
  just crash. This will change behavior of the `NvmeDriver`
  in prod, but if we see a bad device we will still see
  key errors in our logs.
@mattkur mattkur requested review from a team as code owners December 22, 2024 15:57

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

vm/devices/storage/disk_nvme/nvme_driver/fuzz/fuzz_nvme_driver.rs:108

  • The word 'anyhing' is misspelled. It should be 'anything'.
/// error or the executed action. `NvmeDriver` is not intended to be an interface consumed by anyhing ther than `NvmeDisk`, yet the fuzzer targets the driver directly.
@mattkur mattkur merged commit 8171cea into microsoft:main Jan 8, 2025
25 checks passed
@eric135
Copy link
Contributor

eric135 commented Jan 8, 2025

Trying to understand the TODO comments. Do the tags in these refer to anything specific?

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

Successfully merging this pull request may close these issues.

5 participants