)]}'
{
  "commit": "8cd162ce230b154e564a1285bb5f89fcf73f0dce",
  "tree": "aaace0250b44a77d71cd650edaa395d9b3f891e7",
  "parents": [
    "5b16a2212f1840b63d6cc476b26ff9349dab185e"
  ],
  "author": {
    "name": "Peter Zijlstra",
    "email": "peterz@infradead.org",
    "time": "Wed Oct 15 20:37:23 2008 +0200"
  },
  "committer": {
    "name": "Ingo Molnar",
    "email": "mingo@elte.hu",
    "time": "Wed Oct 15 20:43:27 2008 +0200"
  },
  "message": "sched: only update rq-\u003eclock while holding rq-\u003elock\n\nVatsa noticed rq-\u003eclock going funny and tracked it down to an update_rq_clock()\noutside a rq-\u003elock section.\n\nThis is a problem because things like double_rq_lock() update the rq-\u003eclock\nvalue for both rqs. Therefore disabling interrupts isn\u0027t strong enough.\n\nReported-by: Srivatsa Vaddagiri \u003cvatsa@linux.vnet.ibm.com\u003e\nSigned-off-by: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6f230596bd0c1d21a2c68ffbff8207e93dcd65b5",
      "old_mode": 33188,
      "old_path": "kernel/sched.c",
      "new_id": "c530b84c7f80de1225cb8d244a220adf3b817af5",
      "new_mode": 33188,
      "new_path": "kernel/sched.c"
    }
  ]
}