)]}'
{
  "commit": "bb9ff576fdff48c242876f55098a3ee20a29df5d",
  "tree": "65a9ef062fdcab046fa9d4624fcafdbdbe42f150",
  "parents": [
    "3f9f0252130e7dd60d41be0802bf58f6471c691d"
  ],
  "author": {
    "name": "Vitaly Kuznetsov",
    "email": "vkuznets@redhat.com",
    "time": "Mon Dec 22 15:46:46 2025 +0100"
  },
  "committer": {
    "name": "Jason A. Donenfeld",
    "email": "Jason@zx2c4.com",
    "time": "Mon Dec 22 16:18:54 2025 +0100"
  },
  "message": "virt: vmgenid: remap memory as decrypted\n\nIt was found that AWS SEV-SNP enabled instances are not able to boot with\ncommit 81256a50aa0f (\"x86/mm: Make memremap(MEMREMAP_WB) map memory as\nencrypted by default\") applied and the reason seems to be the vmgenid\ndevice which requires unencrypted writeable memory.\n\nA similar problem was previously fixed in DRM with commit\n7dfede7d7edd (\"drm/vmwgfx: Fix guests running with TDX/SEV\").\n\nNote, trusting vmgenid device in a Confidential VM is questionable: the\nmalicious host may intentionally avoid notifying the guest when a copy is\ncreated.\n\nFixes: 81256a50aa0f (\"x86/mm: Make memremap(MEMREMAP_WB) map memory as encrypted by default\")\nSigned-off-by: Vitaly Kuznetsov \u003cvkuznets@redhat.com\u003e\nCc: stable@vger.kernel.org # 6.15+\nSigned-off-by: Jason A. Donenfeld \u003cJason@zx2c4.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "66135eac3abffa3b65e39efc97c217a3da13c287",
      "old_mode": 33188,
      "old_path": "drivers/virt/vmgenid.c",
      "new_id": "2cf0096aa217fbe2b3743b5b296a5100ff7406ea",
      "new_mode": 33188,
      "new_path": "drivers/virt/vmgenid.c"
    }
  ]
}