Page MenuHomeFreeBSD

arm: Zero padding in mcontext_vfp_t in get_vfpcontext().
ClosedPublic

Authored by jhb on Mar 17 2022, 10:34 PM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 13 2024, 9:33 PM
Unknown Object (File)
Jan 1 2024, 4:49 AM
Unknown Object (File)
Dec 23 2023, 11:53 PM
Unknown Object (File)
Dec 20 2023, 5:48 AM
Unknown Object (File)
Dec 20 2023, 1:08 AM
Unknown Object (File)
Nov 1 2023, 1:53 PM
Unknown Object (File)
Sep 26 2023, 2:31 PM
Unknown Object (File)
Sep 9 2023, 6:03 PM
Subscribers

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

jhb requested review of this revision.Mar 17 2022, 10:34 PM
This revision is now accepted and ready to land.Mar 17 2022, 10:38 PM

So it's fine as is, but a pad might be better...

sys/arm/arm/exec_machdep.c
113

Or we could add a a 'mcv_pad' int32_t field and just set that... It's the only bytes that need to be set and setting the other 32*8+4 (260 bytes)....

sys/arm/arm/exec_machdep.c
113

We should put a pad field in as the compiler could still leak kernel stack data via the padding.

sys/arm/arm/exec_machdep.c
113

Modern compilers are smart enough given that memcpy and memset are builtins to only memset the bits that aren't overwritten by the memcpy. I'm not sure of the value of making the padding field explicit?