aboutsummaryrefslogtreecommitdiff
path: root/lib/test_fortify/write_overflow-strlcpy-src.c
diff options
context:
space:
mode:
authorRicardo Koller <[email protected]>2022-05-09 17:16:32 -0700
committerMarc Zyngier <[email protected]>2022-05-16 13:58:04 +0100
commita1ccfd6f6e06eceb632cc29c4f15a32860f05a7e (patch)
treeba73bfaf755f6b8ca9947a79b6b983670840931f /lib/test_fortify/write_overflow-strlcpy-src.c
parent243b1f6c8f0748bd7b03eab17323f1187e580771 (diff)
KVM: arm64: vgic: Do not ignore vgic_its_restore_cte failures
Restoring a corrupted collection entry (like an out of range ID) is being ignored and treated as success. More specifically, a vgic_its_restore_cte failure is treated as success by vgic_its_restore_collection_table. vgic_its_restore_cte uses positive and negative numbers to return error, and +1 to return success. The caller then uses "ret > 0" to check for success. Fix this by having vgic_its_restore_cte only return negative numbers on error. Do this by changing alloc_collection return codes to only return negative numbers on error. Signed-off-by: Ricardo Koller <[email protected]> Reviewed-by: Oliver Upton <[email protected]> Signed-off-by: Marc Zyngier <[email protected]> Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'lib/test_fortify/write_overflow-strlcpy-src.c')
0 files changed, 0 insertions, 0 deletions