diff options
| author | Marc Zyngier <[email protected]> | 2023-09-27 10:09:06 +0100 |
|---|---|---|
| committer | Oliver Upton <[email protected]> | 2023-09-30 18:15:43 +0000 |
| commit | 5f4bd815ec718992c09de1f39479ae90dcbb7df3 (patch) | |
| tree | b519fd303ad9ee8ec95d7060ef3bff4947f962d7 /lib/test_fortify/write_overflow-memcpy.c | |
| parent | ac0fe56d46c0d534dddcf97d132c222722b9b7a5 (diff) | |
KVM: arm64: Use vcpu_idx for invalidation tracking
While vcpu_id isn't necessarily a bad choice as an identifier for
the currently running vcpu, it is provided by userspace, and there
is close to no guarantee that it would be unique.
Switch it to vcpu_idx instead, for which we have much stronger
guarantees.
Reviewed-by: Zenghui Yu <[email protected]>
Signed-off-by: Marc Zyngier <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Oliver Upton <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions