)]}'
{
  "commit": "07708c4af1346ab1521b26a202f438366b7bcffd",
  "tree": "23c82057ddea6d47e74b3db6619e6098b81651b2",
  "parents": [
    "b90c062c65cc8839edfac39778a37a55ca9bda36"
  ],
  "author": {
    "name": "Jan Kiszka",
    "email": "jan.kiszka@siemens.com",
    "time": "Mon Aug 03 18:43:28 2009 +0200"
  },
  "committer": {
    "name": "Avi Kivity",
    "email": "avi@redhat.com",
    "time": "Thu Sep 10 08:33:20 2009 +0300"
  },
  "message": "KVM: x86: Disallow hypercalls for guest callers in rings \u003e 0\n\nSo far unprivileged guest callers running in ring 3 can issue, e.g., MMU\nhypercalls. Normally, such callers cannot provide any hand-crafted MMU\ncommand structure as it has to be passed by its physical address, but\nthey can still crash the guest kernel by passing random addresses.\n\nTo close the hole, this patch considers hypercalls valid only if issued\nfrom guest ring 0. This may still be relaxed on a per-hypercall base in\nthe future once required.\n\nCc: stable@kernel.org\nSigned-off-by: Jan Kiszka \u003cjan.kiszka@siemens.com\u003e\nSigned-off-by: Avi Kivity \u003cavi@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fa525d511d9276a0b5d011c600b499ac9dd36860",
      "old_mode": 33188,
      "old_path": "arch/x86/kvm/x86.c",
      "new_id": "92b5eddaa877e68ea20e2f24fe877ed0042ef3bd",
      "new_mode": 33188,
      "new_path": "arch/x86/kvm/x86.c"
    },
    {
      "type": "modify",
      "old_id": "3ddce03766caf5796f84f71bd7462f117c9a064a",
      "old_mode": 33188,
      "old_path": "include/linux/kvm_para.h",
      "new_id": "d73109243fda075cdd6ef6be7860b917c5612787",
      "new_mode": 33188,
      "new_path": "include/linux/kvm_para.h"
    }
  ]
}