)]}'
{
  "commit": "9c95e7319ba98585ebb6d304eca2d56f401ed70c",
  "tree": "b650a409da9c1e1feb289cfb16ce2fa05c602216",
  "parents": [
    "1799e35d5baab6e06168b46cc78b968e728ea3d1"
  ],
  "author": {
    "name": "Hiroshi Shimamoto",
    "email": "h-shimamoto@ct.jp.nec.com",
    "time": "Wed Sep 19 23:34:46 2007 +0200"
  },
  "committer": {
    "name": "Ingo Molnar",
    "email": "mingo@elte.hu",
    "time": "Wed Sep 19 23:34:46 2007 +0200"
  },
  "message": "sched: fix invalid sched_class use\n\nWhen using rt_mutex, a NULL pointer dereference is occurred at\nenqueue_task_rt. Here is a scenario;\n1) there are two threads, the thread A is fair_sched_class and\n   thread B is rt_sched_class.\n2) Thread A is boosted up to rt_sched_class, because the thread A\n   has a rt_mutex lock and the thread B is waiting the lock.\n3) At this time, when thread A create a new thread C, the thread\n   C has a rt_sched_class.\n4) When doing wake_up_new_task() for the thread C, the priority\n   of the thread C is out of the RT priority range, because the\n   normal priority of thread A is not the RT priority. It makes\n   data corruption by overflowing the rt_prio_array.\nThe new thread C should be fair_sched_class.\n\nThe new thread should be valid scheduler class before queuing.\nThis patch fixes to set the suitable scheduler class.\n\nSigned-off-by: Hiroshi Shimamoto \u003ch-shimamoto@ct.jp.nec.com\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\nSigned-off-by: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "63e0971c8fbb644b21d77a7393da6dc5b4c41df1",
      "old_mode": 33188,
      "old_path": "kernel/sched.c",
      "new_id": "6107a0cd6325f9afe219007e1e1e446fda899b78",
      "new_mode": 33188,
      "new_path": "kernel/sched.c"
    }
  ]
}