)]}'
{
  "commit": "7cbc5b8d4a775a43875a09e29c49a2a8195b5b2d",
  "tree": "b172a445ca84bd463abc6006233799e0a5f422b2",
  "parents": [
    "9905ce8ad7b79dddd23c7b4753d0b2cdb65bde3c"
  ],
  "author": {
    "name": "Jiri Olsa",
    "email": "jolsa@redhat.com",
    "time": "Tue May 10 12:43:46 2011 +0200"
  },
  "committer": {
    "name": "Steven Rostedt",
    "email": "rostedt@goodmis.org",
    "time": "Wed May 25 19:56:36 2011 -0400"
  },
  "message": "jump_label: Check entries limit in __jump_label_update\n\nWhen iterating the jump_label entries array (core or modules),\nthe __jump_label_update function peeks over the last entry.\n\nThe reason is that the end of the for loop depends on the key\nvalue of the processed entry. Thus when going through the\nlast array entry, we will touch the memory behind the array\nlimit.\n\nThis bug probably will never be triggered, since most likely the\nmemory behind the jump_label entries will be accesable and the\nentry-\u003ekey will be different than the expected value.\n\nSigned-off-by: Jiri Olsa \u003cjolsa@redhat.com\u003e\nAcked-by: Jason Baron \u003cjbaron@redhat.com\u003e\nLink: http://lkml.kernel.org/r/20110510104346.GC1899@jolsa.brq.redhat.com\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "74d1c099fbd1d8a8a3368865f919e978020e3521",
      "old_mode": 33188,
      "old_path": "kernel/jump_label.c",
      "new_id": "fa27e750dbc0edb3dd5c502da1b5be38d83d8c8b",
      "new_mode": 33188,
      "new_path": "kernel/jump_label.c"
    }
  ]
}