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

kani: fix infinite loop unwinding in dumbo harnesses #5083

Merged
merged 4 commits into from
Mar 13, 2025

Conversation

roypat
Copy link
Contributor

@roypat roypat commented Mar 13, 2025

Since 0.58.0 kani gets stuck unwinding loops in the dumbo proofs. The exact loops were the ones in the byte_order module. We've previously seen this with a subset of the byte_order functions, which is why some of them were already stubbed out in kani. However, instead of just doing more stubbing, let's just eliminate the loops. The were just a handrolled memcpy (the reason we need these convoluted byte_order functions in the first place is that the stdlib functions cannot deal with buffers that are "too small", while we for some reason want to support that).

Signed-off-by: Patrick Roy roypat@amazon.co.uk## Changes

...

Reason

...

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.

PR Checklist

  • I have read and understand CONTRIBUTING.md.
  • I have run tools/devtool checkstyle to verify that the PR passes the
    automated style checks.
  • I have described what is done in these changes, why they are needed, and
    how they are solving the problem in a clear and encompassing way.
  • I have updated any relevant documentation (both in code and in the docs)
    in the PR.
  • I have mentioned all user-facing changes in CHANGELOG.md.
  • If a specific issue led to this PR, this PR closes the issue.
  • When making API changes, I have followed the
    Runbook for Firecracker API changes.
  • I have tested all new and changed functionalities in unit tests and/or
    integration tests.
  • I have linked an issue to every new TODO.

  • This functionality cannot be added in rust-vmm.

roypat added 2 commits March 13, 2025 12:13
--enable-unstable and --restrict-vtable got deprecated in kani 0.59.0 in
favor of variants based on -Z flags. So use the -Z flags instead

Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
rebuilding the docker container can upgrade kani, and we'd like to know
at the PR stage if that causes issues (such as timeouts).

Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
Copy link

codecov bot commented Mar 13, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.15%. Comparing base (7c0dc1e) to head (b606d1b).
Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5083      +/-   ##
==========================================
- Coverage   83.15%   83.15%   -0.01%     
==========================================
  Files         248      248              
  Lines       26901    26896       -5     
==========================================
- Hits        22370    22365       -5     
  Misses       4531     4531              
Flag Coverage Δ
5.10-c5n.metal 83.52% <100.00%> (-0.01%) ⬇️
5.10-m5n.metal 83.50% <100.00%> (+<0.01%) ⬆️
5.10-m6a.metal 82.71% <100.00%> (-0.01%) ⬇️
5.10-m6g.metal 79.60% <100.00%> (-0.01%) ⬇️
5.10-m6i.metal 83.49% <100.00%> (-0.01%) ⬇️
5.10-m7g.metal 79.60% <100.00%> (-0.01%) ⬇️
6.1-c5n.metal 83.56% <100.00%> (-0.01%) ⬇️
6.1-m5n.metal 83.54% <100.00%> (-0.01%) ⬇️
6.1-m6a.metal 82.75% <100.00%> (-0.01%) ⬇️
6.1-m6g.metal 79.60% <100.00%> (+0.05%) ⬆️
6.1-m6i.metal 83.54% <100.00%> (-0.01%) ⬇️
6.1-m7g.metal 79.60% <100.00%> (+0.05%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@roypat roypat added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label Mar 13, 2025
@roypat roypat requested a review from Manciukic March 13, 2025 15:26
@roypat roypat force-pushed the kani-deprecation-cleanup branch from 00fd35c to 275003a Compare March 13, 2025 15:37
JackThomson2
JackThomson2 previously approved these changes Mar 13, 2025
roypat added 2 commits March 13, 2025 16:44
Instead of copying the buffers byte-by-byte in a loop, just use
copy_from_slice, which compiles to a memcpy.

While we're at it, drop some unused function definitions.

Also remove the special snowflake functions for dealing with i8 slices,
and instead just use zerocopy to safely transmute these into u8 slices,
on which the normal functions work.

Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
with the byte_order modules no longer using loops, this is no longer
needed.

Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
@roypat roypat enabled auto-merge (rebase) March 13, 2025 17:09
@roypat roypat merged commit dd0d932 into firecracker-microvm:main Mar 13, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Awaiting review Indicates that a pull request is ready to be reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants