)]}'
{
  "commit": "74a03b69d1b5ce00a568e142ca97e76b7f5239c6",
  "tree": "02bdea43ae6d528dcee97c00c3a8651f8841411a",
  "parents": [
    "091438dd5668396328a3419abcbc6591159eb8d1"
  ],
  "author": {
    "name": "john stultz",
    "email": "johnstul@us.ibm.com",
    "time": "Fri May 01 13:10:25 2009 -0700"
  },
  "committer": {
    "name": "Thomas Gleixner",
    "email": "tglx@linutronix.de",
    "time": "Sat May 02 10:22:27 2009 +0200"
  },
  "message": "clockevents: prevent endless loop in tick_handle_periodic()\n\ntick_handle_periodic() can lock up hard when a one shot clock event\ndevice is used in combination with jiffies clocksource.\n\nAvoid an endless loop issue by requiring that a highres valid\nclocksource be installed before we call tick_periodic() in a loop when\nusing ONESHOT mode. The result is we will only increment jiffies once\nper interrupt until a continuous hardware clocksource is available.\n\nWithout this, we can run into a endless loop, where each cycle through\nthe loop, jiffies is updated which increments time by tick_period or\nmore (due to clock steering), which can cause the event programming to\nthink the next event was before the newly incremented time and fail\ncausing tick_periodic() to be called again and the whole process loops\nforever.\n\n[ Impact: prevent hard lock up ]\n\nSigned-off-by: John Stultz \u003cjohnstul@us.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: stable@kernel.org\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "21a5ca849514b40b689c5b34e2c9caaf9cbf051b",
      "old_mode": 33188,
      "old_path": "kernel/time/tick-common.c",
      "new_id": "83c4417b6a3cccd734c8f7f9386670641babd0c8",
      "new_mode": 33188,
      "new_path": "kernel/time/tick-common.c"
    }
  ]
}