)]}'
{
  "commit": "11d7e4f57f688287511f911187ada11784b4263d",
  "tree": "b02cbcbc876acdeb045aed46433e5a0f83254f12",
  "parents": [
    "0b84d89c30eefd3318d039e5660f03ffb2ecb24c"
  ],
  "author": {
    "name": "Kalesh Singh",
    "email": "kaleshsingh@google.com",
    "time": "Thu Jan 25 16:10:27 2024 -0800"
  },
  "committer": {
    "name": "Kalesh Singh",
    "email": "kaleshsingh@google.com",
    "time": "Thu Feb 01 18:13:33 2024 +0000"
  },
  "message": "ANDROID: mm: Fix VMA ref count after fast-mremap\n\nSince the cmpxchg() to unlock the VMA (reset ref count from -1), is\nenclosed in VM_BUG_ON_VMA() it gets compiled out in non-debug builds\n(CONFIG_DEBUG_VM\u003dn). This means that any VMA that underwent a fast-remap\nwill have it\u0027s refcount stuck at -1, making it not be eligible for\nfuture speculative faults, and preventing freeing of the VMA.\n\nBug: 323371343\nBug: 322411509\nChange-Id: If5bf61c7d94268700f2c4f096d946201b68abdb8\nSigned-off-by: Kalesh Singh \u003ckaleshsingh@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a6484e84570654d8967bb0dc809e75da87c2986f",
      "old_mode": 33188,
      "old_path": "mm/mremap.c",
      "new_id": "fa90d4b7aa0eb38f8ba630aea8b09793e0e7b7a7",
      "new_mode": 33188,
      "new_path": "mm/mremap.c"
    }
  ]
}
