rust: Ignore preserve-most functions
PATCH 1/1 rust: Ignore preserve-most functions
Neither bindgen nor Rust know about the preserve-most calling convention, and Clang describes it as unstable. Since we aren't using functions with this calling convention from Rust, blocklist them.
These functions are only added to the build when list hardening is enabled, which is likely why others didn't notice this yet.
--- rust/bindgen_parameters | 4 ++++ 1 file changed, 4 insertions(+)
rust/bindgen_parameters +4 -0
@@ -20,3 +20,7 @@ # `seccomp`'s comment gets understood as a doctest --no-doc-comments + +# These functions use the __preserve_most calling convention, which neither bindgen +# nor Rust currently understand, and which Clang currently declares to be unstable. +--blocklist-function __list_.*_report
Signature · 1 line
2.42.0.820.g83a721a137-goog
Quoted 9 lines · Matthew Maurer
Neither bindgen nor Rust know about the preserve-most calling convention, and Clang describes it as unstable. Since we aren't using functions with this calling convention from Rust, blocklist them.
These functions are only added to the build when list hardening is enabled, which is likely why others didn't notice this yet.
Signed-off-by Matthew Maurer <[email protected]>
Quoted 10 lines · Matthew Maurer
Neither bindgen nor Rust know about the preserve-most calling convention, and Clang describes it as unstable. Since we aren't using functions with this calling convention from Rust, blocklist them.
These functions are only added to the build when list hardening is enabled, which is likely why others didn't notice this yet.
Signed-off-by Matthew Maurer <[email protected]>---
[...]
Miguel Ojeda
AppliedQuoted 9 lines · Matthew Maurer
Neither bindgen nor Rust know about the preserve-most calling convention, and Clang describes it as unstable. Since we aren't using functions with this calling convention from Rust, blocklist them.
These functions are only added to the build when list hardening is enabled, which is likely why others didn't notice this yet.
Signed-off-by Matthew Maurer <[email protected]>
Applied to rust-next (used Markdown for consistency with the other comments in the file).
Thanks everyone!
Cheers,
Miguel