)]}'
{
  "commit": "7a450a1981e92aa1df60874ba8368d605f206743",
  "tree": "335055084c303f0f1ba9e4568f56e981bcbe4bd9",
  "parents": [
    "966e5c39333abb8314244a3bc54a0ffa39b06d92"
  ],
  "author": {
    "name": "Will Deacon",
    "email": "willdeacon@google.com",
    "time": "Mon Jul 03 14:39:53 2023 +0100"
  },
  "committer": {
    "name": "Fuad Tabba",
    "email": "tabba@google.com",
    "time": "Thu Sep 07 16:03:29 2023 +0100"
  },
  "message": "KVM: arm64: Introduce new spinlock for hypervisor VM vCPUs[] array\n\nThe vCPU structures of the hypervisor VM struct claim to be protected\nby \u0027vm_table_lock\u0027, however:\n\n  1. This doesn\u0027t appear to be the case on the PSCI paths, where the\n     array is walked locklessly when accessing the target vCPU\n\n  2. The \u0027vm_table_lock\u0027 serialises across all VMs, so is overkill\n\nIntroduce a new per-VM spinlock for the vCPU array and ensure that it is\nheld whilst accessing the data structure.\n\nSigned-off-by: Will Deacon \u003cwill@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4dce3189903d3aaa554d08f2d2643a07013e896f",
      "old_mode": 33188,
      "old_path": "arch/arm64/kvm/hyp/include/nvhe/pkvm.h",
      "new_id": "ecd55e4aca5d682eb8d5827250aef261b9dd89d8",
      "new_mode": 33188,
      "new_path": "arch/arm64/kvm/hyp/include/nvhe/pkvm.h"
    },
    {
      "type": "modify",
      "old_id": "8b22abff6eabfa4aa67ef0e02210b92ad7acc336",
      "old_mode": 33188,
      "old_path": "arch/arm64/kvm/hyp/nvhe/pkvm.c",
      "new_id": "4cc03527263136b866e997d4417a384597245f84",
      "new_mode": 33188,
      "new_path": "arch/arm64/kvm/hyp/nvhe/pkvm.c"
    }
  ]
}