Fix in order to enable the cmse_nonsecure_entry attribute securely in Rust #76
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.
Hello 👋
Following the process described here to add an upstreamed bug fix in Rust's fork.
The PR enabling the
cmse_nonsecure_entry
in Rust is open here.The specific comment that started the need of this bug fix is here.
Without this bug fix, the
cmse_nonsecure_entry
attribute will be a source of security problems (seg faults, information disclosure) if a function with more than 4u32
arguments is decorated with it.Original review in LLVM.