)]}'
{
  "commit": "90675a27fa3eb0e97f1d040b183cceb44316e669",
  "tree": "cf97bd53de877c12798368a4e06bba21285c0763",
  "parents": [
    "7a434814c7a6500b08bf4419ba8712b152d08d08"
  ],
  "author": {
    "name": "Daniel Walker",
    "email": "dwalker@mvista.com",
    "time": "Tue Mar 06 01:42:11 2007 -0800"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@woody.linux-foundation.org",
    "time": "Tue Mar 06 09:30:25 2007 -0800"
  },
  "message": "[PATCH] fix vsyscall settimeofday\n\nI\u0027ve only seen this on x86_64.\n\nThe vsyscall state only gets updated when a timer interrupts comes in.  So\nif the time is set long before the next timer, there will be a period when\na gettimeofday() won\u0027t reflect the correct time.\n\nI added an explicit update_vsyscall() during the settimeofday(), that way\nthe vsyscall state doesn\u0027t get stale.\n\nSigned-off-by: Daniel Walker \u003cdwalker@mvista.com\u003e\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nAcked-by: Ingo Molnar \u003cmingo@elte.hu\u003e\nAcked-by: John Stultz \u003cjohnstul@us.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ee0a2da4aab33e86df8d625e0cb9dcdd82a009e7",
      "old_mode": 33188,
      "old_path": "kernel/timer.c",
      "new_id": "797cccb86431c1a423647141b62270f124c341dc",
      "new_mode": 33188,
      "new_path": "kernel/timer.c"
    }
  ]
}