)]}'
{
  "commit": "eda9cec4c9a12208a6f69fbe68f72a6311d50032",
  "tree": "36d9d40657db3ee47c3c38f9d255b6e763539628",
  "parents": [
    "675357362aeba19688440eb1aaa7991067f73b12"
  ],
  "author": {
    "name": "Josh Poimboeuf",
    "email": "jpoimboe@redhat.com",
    "time": "Fri Nov 03 07:58:54 2017 -0500"
  },
  "committer": {
    "name": "Ingo Molnar",
    "email": "mingo@kernel.org",
    "time": "Sun Nov 05 09:52:16 2017 +0100"
  },
  "message": "x86/module: Detect and skip invalid relocations\n\nThere have been some cases where external tooling (e.g., kpatch-build)\ncreates a corrupt relocation which targets the wrong address.  This is a\nsilent failure which can corrupt memory in unexpected places.\n\nOn x86, the bytes of data being overwritten by relocations are always\ninitialized to zero beforehand.  Use that knowledge to add sanity checks\nto detect such cases before they corrupt memory.\n\nSigned-off-by: Josh Poimboeuf \u003cjpoimboe@redhat.com\u003e\nCc: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nCc: Peter Zijlstra \u003cpeterz@infradead.org\u003e\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: jeyu@kernel.org\nCc: live-patching@vger.kernel.org\nLink: http://lkml.kernel.org/r/37450d6c6225e54db107fba447ce9e56e5f758e9.1509713553.git.jpoimboe@redhat.com\n[ Restructured the messages, as it\u0027s unclear whether the relocation or the target is corrupted. ]\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "62e7d70aadd5ffece72b357ac1e3024a1b9f7897",
      "old_mode": 33188,
      "old_path": "arch/x86/kernel/module.c",
      "new_id": "da0c160e558905c2164bf1d3879bd1a1cf368f34",
      "new_mode": 33188,
      "new_path": "arch/x86/kernel/module.c"
    }
  ]
}
