)]}'
{
  "commit": "d7b41a24bfb5d7fa02f7b49be1293d468814e424",
  "tree": "37c206c5125aca1084b8c4d76f80c5de4dec7c38",
  "parents": [
    "c3bf9bc243092c53946fd6d8ebd6dc2f4e572d48"
  ],
  "author": {
    "name": "Bodo Stroesser",
    "email": "bstroesser@fujitsu-siemens.com",
    "time": "Sat Apr 26 14:10:16 2008 -0700"
  },
  "committer": {
    "name": "Thomas Gleixner",
    "email": "tglx@linutronix.de",
    "time": "Sun Apr 27 18:26:43 2008 +0200"
  },
  "message": "hrtimer: timeout too long when using HRTIMER_CB_SOFTIRQ\n\nWhen using hrtimer with timer-\u003ecb_mode \u003d\u003d HRTIMER_CB_SOFTIRQ\nin some cases the clockevent is not programmed.\nThis happens, if:\n - a timer is rearmed while it\u0027s state is HRTIMER_STATE_CALLBACK\n - hrtimer_reprogram() returns -ETIME, when it is called after\n   CALLBACK is finished. This occurs if the new timer-\u003eexpires\n   is in the past when CALLBACK is done.\nIn this case, the timer needs to be removed from the tree and put\nonto the pending list again.\n\nThe patch is against 2.6.22.5, but AFAICS, it is relevant\nfor 2.6.25 also (in run_hrtimer_pending()).\n\nSigned-off-by: Bodo Stroesser \u003cbstroesser@fujitsu-siemens.com\u003e\nCc: stable@kernel.org\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f78777abe769e1e3608b8f751d1c996f05aeea13",
      "old_mode": 33188,
      "old_path": "kernel/hrtimer.c",
      "new_id": "e379ef0e9c20c5e77b0003398e46eb859c6399e3",
      "new_mode": 33188,
      "new_path": "kernel/hrtimer.c"
    }
  ]
}