)]}'
{
  "commit": "b91aac29bb9b7cab34b0297449bd2a16944b83d9",
  "tree": "dfe8da51342362245fa39943f57c41c1c0aa4ef9",
  "parents": [
    "8647af71d623671a020a54d860f77bc0fa2e606e"
  ],
  "author": {
    "name": "Jesper Juhl",
    "email": "jesper.juhl@gmail.com",
    "time": "Sat Mar 08 02:16:07 2008 +0100"
  },
  "committer": {
    "name": "Greg Kroah-Hartman",
    "email": "gregkh@suse.de",
    "time": "Mon Mar 10 16:38:02 2008 -0700"
  },
  "message": "PCI Hotplug: Fix small mem leak in IBM Hot Plug Controller Driver\n\nIn drivers/pci/hotplug/ibmphp_ebda.c::ebda_rsrc_controller(), storage is\nallocated with kzalloc() and assigned to \u0027tmp_slot\u0027.  Then lots of\nstuff, like -\u003eflag, -\u003esupported_speed etc is set in tmp_slot.  A bit\nfurther down there\u0027s then this test :\n\n  if (!bus_info_ptr1) {\n    rc \u003d -ENODEV;\n    goto error;\n  }\n\nAt this point, tmp_slot has not been assigned to anything, so when\nerroring-out we want to free it, but nothing at the \u0027error:\u0027 label\nfree\u0027s \u0027tmp_slot\u0027 - and we can\u0027t really free \u0027tmp_slot\u0027 at \u0027error:\u0027\nsince we may jump to that label later when \u0027tmp_slot\u0027 *has* been used\nand we do not want it freed. So, the only sane option left seems to be\nto kfree(tmp_slot) just before jumping to the \u0027error:\u0027 label in the one\nplace where this is what actually makes sense. The following patch does\njust that and thus kills off a tiny potential memory leak.\n\n\nSigned-off-by: Jesper Juhl \u003cjesper.juhl@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "600ed7b67ae7fab1f748d2d99cfee8a3dc516de4",
      "old_mode": 33188,
      "old_path": "drivers/pci/hotplug/ibmphp_ebda.c",
      "new_id": "bbccde9f228f1c25dd183dd7899e3bda3524006f",
      "new_mode": 33188,
      "new_path": "drivers/pci/hotplug/ibmphp_ebda.c"
    }
  ]
}