seccomp: allow sendto for vsock thread #7477
Merged
+1
−0
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.
As of rust 1.90, writes to unix socket streams use send_with_flags instead of write, so it uses a sendto syscall instead of write.
I found this when upgrading my machines to a new Nixpkgs which bumped rust from 1.89 to 1.90. Suddenly, all of my VMs were crashlooping due to seccomp violations.
--seccomp logshowed this as the culprit, and with this patch, I'm not seeing any more audit logs.