)]}'
{
  "commit": "4031ff388138b58e5cd472dccce38828bcb8c706",
  "tree": "f2c88fdcdef3ec9880d23ce271f14e95f7aa1cf5",
  "parents": [
    "c723e084606ca1c81e91b80b2c0c44bde7bbc4df"
  ],
  "author": {
    "name": "Aleksey Gorelov",
    "email": "Aleksey_Gorelov@Phoenix.com",
    "time": "Tue Jun 27 02:53:48 2006 -0700"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@g5.osdl.org",
    "time": "Tue Jun 27 17:32:38 2006 -0700"
  },
  "message": "[PATCH] fix broken vm86 interrupt/signal handling\n\nCommit c3ff8ec31c1249d268cd11390649768a12bec1b9 (\"[PATCH] i386: Don\u0027t\nmiss pending signals returning to user mode after signal processing\")\nmeant that vm86 interrupt/signal handling got broken for the case when\nvm86 is called from kernel space.\n\nIn this scenario, if signal is pending because of vm86 interrupt,\ndo_notify_resume/do_signal exits immediately due to user_mode() check,\nwithout processing any signals.  Thus, resume_userspace handler is spinning\nin a tight loop with signal pending and TIF_SIGPENDING is set.  Previously\neverything worked Ok.\n\nNo in-tree usage of vm86() from kernel space exists, but I\u0027ve heard\nabout a number of projects out there which use vm86 calls from kernel,\none of them being this, for instance:\n\n\thttp://dev.gentoo.org/~spock/projects/vesafb-tng/\n\nThe following patch fixes the issue.\n\nSigned-off-by: Aleksey Gorelov \u003caleksey_gorelov@phoenix.com\u003e\nCc: Atsushi Nemoto \u003canemo@mba.ocn.ne.jp\u003e\nCc: Roland McGrath \u003croland@redhat.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8713e0248a0be1d9902b1d813680b20528d46df9",
      "old_mode": 33188,
      "old_path": "arch/i386/kernel/entry.S",
      "new_id": "e8d2630fd19a201973b2df04efc8cc4e9b059cec",
      "new_mode": 33188,
      "new_path": "arch/i386/kernel/entry.S"
    }
  ]
}