diff options
| author | David Engraf <[email protected]> | 2022-02-25 11:40:08 +0100 |
|---|---|---|
| committer | Will Deacon <[email protected]> | 2022-03-07 21:38:25 +0000 |
| commit | 0a32c88ddb9af30e8a16d41d7b9b824c27d29459 (patch) | |
| tree | a4a05b2bcc23ce6d7634bb81ea267b571f17feab /lib/test_fortify/write_overflow-memcpy.c | |
| parent | 0a2eec83c2c23cf609e781732b338a9a4f18e00c (diff) | |
arm64: signal: nofpsimd: Do not allocate fp/simd context when not available
Commit 6d502b6ba1b2 ("arm64: signal: nofpsimd: Handle fp/simd context for
signal frames") introduced saving the fp/simd context for signal handling
only when support is available. But setup_sigframe_layout() always
reserves memory for fp/simd context. The additional memory is not touched
because preserve_fpsimd_context() is not called and thus the magic is
invalid.
This may lead to an error when parse_user_sigframe() checks the fp/simd
area and does not find a valid magic number.
Signed-off-by: David Engraf <[email protected]>
Reviwed-by: Mark Brown <[email protected]>
Fixes: 6d502b6ba1b267b3 ("arm64: signal: nofpsimd: Handle fp/simd context for signal frames")
Cc: <[email protected]> # 5.6.x
Reviewed-by: Catalin Marinas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Will Deacon <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions