)]}'
{
  "commit": "b94de9bb7519f597a3aed521d5eaeb5b02a7cbc0",
  "tree": "1c2771372fc23c55dd678080aa6529c98f8de371",
  "parents": [
    "a2b6bf63cb7a3e34bd2e753a6f2c2776b5c8496f"
  ],
  "author": {
    "name": "Chris Wilson",
    "email": "chris@chris-wilson.co.uk",
    "time": "Wed Jul 28 22:59:02 2010 +0100"
  },
  "committer": {
    "name": "Catalin Marinas",
    "email": "catalin.marinas@arm.com",
    "time": "Wed Jul 28 22:59:02 2010 +0100"
  },
  "message": "lib/scatterlist: Hook sg_kmalloc into kmemleak (v2)\n\nkmemleak ignores page_alloc() and so believes the final sub-page\nallocation using the plain kmalloc is decoupled and lost. This leads to\nlots of false-positives with code that uses scatterlists.\n\nThe options seem to be either to tell kmemleak that the kmalloc is not\nleaked or to notify kmemleak of the page allocations. The danger of the\nfirst approach is that we may hide a real leak, so choose the latter\napproach (of which I am not sure of the downsides).\n\nv2: Added comments on the suggestion of Catalin.\n\nSigned-off-by: Chris Wilson \u003cchris@chris-wilson.co.uk\u003e\nCc: Tejun Heo \u003ctj@kernel.org\u003e\nCc: Jens Axboe \u003cjaxboe@fusionio.com\u003e\nSigned-off-by: Catalin Marinas \u003ccatalin.marinas@arm.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9afa25b52a83f33f0685d94306f1df4def372db4",
      "old_mode": 33188,
      "old_path": "lib/scatterlist.c",
      "new_id": "a5ec42868f99d8d6700f34ca81c061c1ef21d15b",
      "new_mode": 33188,
      "new_path": "lib/scatterlist.c"
    }
  ]
}