diff options
author | Fuad Tabba <tabba@google.com> | 2025-09-09 08:24:28 +0100 |
---|---|---|
committer | Marc Zyngier <maz@kernel.org> | 2025-09-15 10:46:55 +0100 |
commit | f9ac33e45d57bc4aa365363ffb650c830e5bb325 (patch) | |
tree | e654b8ce458f1c25bce2f92dd37463cd5c5ea9fd /scripts/gdb/linux/timerlist.py | |
parent | 1b237f190eb3d36f52dffe07a40b5eb210280e00 (diff) |
KVM: arm64: Add build-time check for duplicate DECLARE_REG use
The DECLARE_REG() macro provides a convenient way to create a local
variable initialized from a cpu context in the hyp trap handlers.
However, a common error is to use the macro multiple times in the same
scope with the same register index, but for different logical purposes.
This results in valid C code that compiles without error, but introduces
subtle bugs where a developer expects two different variables to hold
values from two different registers, when in fact they are both sourced
from the same one.
To prevent this entire class of bugs, modify the DECLARE_REG() macro
to declare a dummy variable whose name is derived from the register
index. If the macro is used again with the same index in the same
scope, the compiler will fail with a "redeclaration of variable"
error, turning a subtle runtime bug into an obvious build-time failure.
Signed-off-by: Fuad Tabba <tabba@google.com>
Tested-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'scripts/gdb/linux/timerlist.py')
0 files changed, 0 insertions, 0 deletions