)]}'
{
  "commit": "7bdb157cdebbf95a1cd94ed2e01b338714075d00",
  "tree": "d3e577e32989820c2559ab0a212d971b2e049139",
  "parents": [
    "659caaf65dc9c7150aa3e80225ec6e66b25ab3ce"
  ],
  "author": {
    "name": "kiyin(尹亮)",
    "email": "kiyin@tencent.com",
    "time": "Wed Nov 04 08:23:22 2020 +0300"
  },
  "committer": {
    "name": "Ingo Molnar",
    "email": "mingo@kernel.org",
    "time": "Sat Nov 07 13:07:26 2020 +0100"
  },
  "message": "perf/core: Fix a memory leak in perf_event_parse_addr_filter()\n\nAs shown through runtime testing, the \"filename\" allocation is not\nalways freed in perf_event_parse_addr_filter().\n\nThere are three possible ways that this could happen:\n\n - It could be allocated twice on subsequent iterations through the loop,\n - or leaked on the success path,\n - or on the failure path.\n\nClean up the code flow to make it obvious that \u0027filename\u0027 is always\nfreed in the reallocation path and in the two return paths as well.\n\nWe rely on the fact that kfree(NULL) is NOP and filename is initialized\nwith NULL.\n\nThis fixes the leak. No other side effects expected.\n\n[ Dan Carpenter: cleaned up the code flow \u0026 added a changelog. ]\n[ Ingo Molnar: updated the changelog some more. ]\n\nFixes: 375637bc5249 (\"perf/core: Introduce address range filtering\")\nSigned-off-by: \"kiyin(尹亮)\" \u003ckiyin@tencent.com\u003e\nSigned-off-by: Dan Carpenter \u003cdan.carpenter@oracle.com\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: \"Srivatsa S. Bhat\" \u003csrivatsa@csail.mit.edu\u003e\nCc: Anthony Liguori \u003caliguori@amazon.com\u003e\n--\n kernel/events/core.c | 12 +++++-------\n 1 file changed, 5 insertions(+), 7 deletions(-)\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "da467e1dd49a2dd3b571245b5c8eeb5adbe73ac6",
      "old_mode": 33188,
      "old_path": "kernel/events/core.c",
      "new_id": "5a29ab09e72d6ac15776ff714d2afb114e118222",
      "new_mode": 33188,
      "new_path": "kernel/events/core.c"
    }
  ]
}