)]}'
{
  "commit": "403f307576396f3362fbb65af190885b6036c72c",
  "tree": "d3737ebe960d65152b7ee119b8b5a7ad2d59e09b",
  "parents": [
    "b090f9fa53d51c8a33370071de9e391919ee1fa7"
  ],
  "author": {
    "name": "Arve Hjønnevåg",
    "email": "arve@android.com",
    "time": "Sat Feb 14 02:07:24 2009 +0100"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@linux-foundation.org",
    "time": "Sat Feb 21 14:17:18 2009 -0800"
  },
  "message": "PM: Fix suspend_console and resume_console to use only one semaphore\n\nThis fixes a race where a thread acquires the console while the\nconsole is suspended, and the console is resumed before this\nthread releases it. In this case, the secondary console\nsemaphore would be left locked, and the primary semaphore would\nbe released twice. This in turn would cause the console switch\non suspend or resume to hang forever.\n\nNote that suspend_console does not actually lock the console\nfor clients that use acquire_console_sem, it only locks it for\nclients that use try_acquire_console_sem. If we change\nsuspend_console to fully lock the console, then the kernel\nmay deadlock on suspend. One client of try_acquire_console_sem\nis acquire_console_semaphore_for_printk, which uses it to\nprevent printk from using the console while it is suspended.\n\nSigned-off-by: Arve Hjønnevåg \u003carve@android.com\u003e\nSigned-off-by: Rafael J. Wysocki \u003crjw@sisk.pl\u003e\nCc: Len Brown \u003clenb@kernel.org\u003e\nCc: Greg KH \u003cgregkh@suse.de\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "69188f226a93251009d22d6dc453ce3d59220816",
      "old_mode": 33188,
      "old_path": "kernel/printk.c",
      "new_id": "e3602d0755b0dd99c9fb47887fd67d371cdd5424",
      "new_mode": 33188,
      "new_path": "kernel/printk.c"
    }
  ]
}