[PATCH 6.6.y+6.1.y 0/2] KVM: x86/mmu: Check write tracking in all address spaces

[Artem Dinaburg <artem@trailofbits.com>]

Please queue upstream commit 0f38453cdb2e17566ccb7c0f3dabd5bd21caca26
("KVM: x86/mmu: Check write tracking in all address spaces") for the
stable trees. It is in mainline as of v7.2-rc6.

The fix is absent by code state from 7.1.10, 6.18.46, 6.12.105, 6.6.153
and 6.1.184.

7.1.y, 6.18.y, 6.12.y: please cherry-pick the upstream commit directly.
No patch is included for these trees. Commit 0f38453cdb2e applies and
compiles unmodified on all three, so there is nothing to adapt:

  git cherry-pick -x 0f38453cdb2e17566ccb7c0f3dabd5bd21caca26

6.6.y and 6.1.y need adapted backports; they are patches 1/2 and 2/2 of
this series. On 6.6 the upstream commit applies but does not build,
because KVM_MAX_NR_ADDRESS_SPACES and kvm_arch_nr_memslot_as_ids() do
not exist there. On 6.1 the upstream commit conflicts: the function is
still kvm_slot_page_track_is_active() and the tracking array is
mode-indexed gfn_track[].

5.15.y and 5.10.y are not covered by this submission. Those trees were
not assessed.

Jinu Kim (2):
  [6.6.y] KVM: x86/mmu: Check write tracking in all address spaces
  [6.1.y] KVM: x86/mmu: Check write tracking in all address spaces

Each patch touches only arch/x86/kvm/mmu/page_track.c:
  1/2 (6.6.y): 26 insertions(+), 6 deletions(-)
  2/2 (6.1.y): 22 insertions(+), 6 deletions(-)

-- 
2.43.0