)]}'
{
  "commit": "b45c6e76bc2c72f6426c14bed64fdcbc9bf37cb0",
  "tree": "5b1d7a869db512f1297c82142adf006c3c6786c0",
  "parents": [
    "bd4f490a079730aadfaf9a728303ea0135c01945"
  ],
  "author": {
    "name": "Andi Kleen",
    "email": "andi@firstfloor.org",
    "time": "Fri Jan 08 14:42:52 2010 -0800"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@linux-foundation.org",
    "time": "Mon Jan 11 09:34:05 2010 -0800"
  },
  "message": "kernel/signal.c: fix kernel information leak with print-fatal-signals\u003d1\n\nWhen print-fatal-signals is enabled it\u0027s possible to dump any memory\nreachable by the kernel to the log by simply jumping to that address from\nuser space.\n\nOr crash the system if there\u0027s some hardware with read side effects.\n\nThe fatal signals handler will dump 16 bytes at the execution address,\nwhich is fully controlled by ring 3.\n\nIn addition when something jumps to a unmapped address there will be up to\n16 additional useless page faults, which might be potentially slow (and at\nleast is not very efficient)\n\nFortunately this option is off by default and only there on i386.\n\nBut fix it by checking for kernel addresses and also stopping when there\u0027s\na page fault.\n\nSigned-off-by: Andi Kleen \u003cak@linux.intel.com\u003e\nCc: Ingo Molnar \u003cmingo@elte.hu\u003e\nCc: Oleg Nesterov \u003coleg@redhat.com\u003e\nCc: \u003cstable@kernel.org\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": "d09692b4037614cf8a596ec229002018ebee9aac",
      "old_mode": 33188,
      "old_path": "kernel/signal.c",
      "new_id": "934ae5e687b960ddf78c939db4b0e55936799243",
      "new_mode": 33188,
      "new_path": "kernel/signal.c"
    }
  ]
}