)]}'
{
  "commit": "1b79fcb646f66682a62cf34f3cc343b1a9706699",
  "tree": "6b9b215b3bac9b46027266fff10a6c53e2665624",
  "parents": [
    "7c9c6aebe8daabece9e78d47727dcdcb757c0a63"
  ],
  "author": {
    "name": "Jorge Boncompte [DTI2]",
    "email": "jorge@dti2.net",
    "time": "Mon May 07 15:17:31 2012 +0000"
  },
  "committer": {
    "name": "David Lamparter",
    "email": "equinox@diac24.net",
    "time": "Mon May 21 15:41:21 2012 +0200"
  },
  "message": "lib: fix thread_cancel_event()\n\n  ospfd was crashing some times on neighbour going down. The cause was that\nospf_nsm_event() was accessing already freed memory in ospf_nbr_delete()\ncall from ospf_nsm_event().\n\n  What happens is that since commit b5043aab (lib: fix incorrect thread\nlist...) now a thread can be on the event and ready lists but\nthread_cancel_event() doesn\u0027t account for that.\n\n* thread.c: (thread_cancel_event) loop on the ready list too to cancel\n  pending events.\n\nSigned-off-by: Jorge Boncompte [DTI2] \u003cjorge@dti2.net\u003e\nSigned-off-by: David Lamparter \u003cequinox@opensourcerouting.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b36c43a9a640b52d78d68fba1e42b3c6958c450d",
      "old_mode": 33188,
      "old_path": "lib/thread.c",
      "new_id": "dd0413b3477a8c4380ab3754c4d09b92458d13b0",
      "new_mode": 33188,
      "new_path": "lib/thread.c"
    }
  ]
}