)]}'
{
  "commit": "e14af7eeb47ea96c52741c5e5fa010d33daf6973",
  "tree": "0b4c1af86e766726ba75873812715706e4044086",
  "parents": [
    "21aa9280b9f4e9e68d3fa8990df6c9d7fd71f994"
  ],
  "author": {
    "name": "Arjan van de Ven",
    "email": "arjan@linux.intel.com",
    "time": "Fri Jan 25 21:08:33 2008 +0100"
  },
  "committer": {
    "name": "Ingo Molnar",
    "email": "mingo@elte.hu",
    "time": "Fri Jan 25 21:08:33 2008 +0100"
  },
  "message": "debug: track and print last unloaded module in the oops trace\n\nBased on a suggestion from Andi:\n\n In various cases, the unload of a module may leave some bad state around\n that causes a kernel crash AFTER a module is unloaded; and it\u0027s then hard\n to find which module caused that.\n\nThis patch tracks the last unloaded module, and prints this as part of the\nmodule list in the oops trace.\n\nRight now, only the last 1 module is tracked; I expect that this is enough\nfor the vast majority of cases where this information matters; if it turns\nout that tracking more is important, we can always extend it to that.\n\n[ mingo@elte.hu: build fix ]\n\nSigned-off-by: Arjan van de Ven \u003carjan@linux.intel.com\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5bbf225ca07a4d665c3575890caa7f37701abe3d",
      "old_mode": 33188,
      "old_path": "kernel/module.c",
      "new_id": "1bb4c5e0d56e330b1de92b5e20fddbd446e9d314",
      "new_mode": 33188,
      "new_path": "kernel/module.c"
    }
  ]
}