seccomp: fix Threaded drive resize crash - #19
Merged
Merged
Conversation
Updating a Threaded drive clones its backing file on the VMM thread. The Rust clone path uses F_DUPFD_CLOEXEC, which the VMM seccomp policy did not allow and caused Firecracker to exit with BadSyscall. Allow that fcntl command in both architecture policies and exercise file rescan with the Threaded engine. Signed-off-by: Tom Ryan <299368098+tomr-fly@users.noreply.github.com>
This was referenced Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes exit 148 when updating a Threaded drive by allowing
F_DUPFD_CLOEXECin the VMM seccomp filters.Stacked on #15.