)]}'
{
  "commit": "da8d5089da6dfd54e5fd05d0c291a63c2bcf6885",
  "tree": "ad9f7deceed846e56e0185976af5c620722ff9ba",
  "parents": [
    "ede6f5aea054d3fb67c78857f7abdee602302043"
  ],
  "author": {
    "name": "Peter Zijlstra",
    "email": "a.p.zijlstra@chello.nl",
    "time": "Wed Jan 07 15:28:57 2009 +0100"
  },
  "committer": {
    "name": "Ingo Molnar",
    "email": "mingo@elte.hu",
    "time": "Wed Jan 07 16:10:54 2009 +0100"
  },
  "message": "sched: fix possible recursive rq-\u003elock\n\nVaidyanathan Srinivasan reported:\n\n \u003e \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n \u003e [ INFO: possible recursive locking detected ]\n \u003e 2.6.28-autotest-tip-sv #1\n \u003e ---------------------------------------------\n \u003e klogd/5062 is trying to acquire lock:\n \u003e  (\u0026rq-\u003elock){++..}, at: [\u003cffffffff8022aca2\u003e] task_rq_lock+0x45/0x7e\n \u003e\n \u003e but task is already holding lock:\n \u003e  (\u0026rq-\u003elock){++..}, at: [\u003cffffffff805f7354\u003e] schedule+0x158/0xa31\n\nWith sched_mc at 2. (it is default-off)\n\nStrictly speaking we\u0027ll not deadlock, because ttwu will not be able to\nplace the migration task on our rq, but since the code can deal with\nboth rqs getting unlocked, this seems the easiest way out.\n\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": "2e3545f57e770830c4fca6702a64e3e2bca510a1",
      "old_mode": 33188,
      "old_path": "kernel/sched.c",
      "new_id": "deb5ac8c12f37c44e71dcc46484149d073430948",
      "new_mode": 33188,
      "new_path": "kernel/sched.c"
    }
  ]
}