)]}'
{
  "commit": "58ded24f0fcb85bddb665baba75892f6ad0f4b8a",
  "tree": "40190011c2c728cfcfae82e105800958ddc92399",
  "parents": [
    "f2cb933501ebc066bf3c4b1836fd8428f8fe9863"
  ],
  "author": {
    "name": "Tyler Hicks",
    "email": "tyhicks@canonical.com",
    "time": "Tue Jan 24 10:02:22 2012 -0600"
  },
  "committer": {
    "name": "Tyler Hicks",
    "email": "tyhicks@canonical.com",
    "time": "Wed Jan 25 14:43:42 2012 -0600"
  },
  "message": "eCryptfs: Fix oops when printing debug info in extent crypto functions\n\nIf pages passed to the eCryptfs extent-based crypto functions are not\nmapped and the module parameter ecryptfs_verbosity\u003d1 was specified at\nloading time, a NULL pointer dereference will occur.\n\nNote that this wouldn\u0027t happen on a production system, as you wouldn\u0027t\npass ecryptfs_verbosity\u003d1 on a production system. It leaks private\ninformation to the system logs and is for debugging only.\n\nThe debugging info printed in these messages is no longer very useful\nand rather than doing a kmap() in these debugging paths, it will be\nbetter to simply remove the debugging paths completely.\n\nhttps://launchpad.net/bugs/913651\n\nSigned-off-by: Tyler Hicks \u003ctyhicks@canonical.com\u003e\nReported-by: Daniel DeFreez\nCc: \u003cstable@vger.kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ff981503b3e388e8b8e907332916f53ac6f49379",
      "old_mode": 33188,
      "old_path": "fs/ecryptfs/crypto.c",
      "new_id": "63ab24510649cc3a3604e9dd603904d9676a2794",
      "new_mode": 33188,
      "new_path": "fs/ecryptfs/crypto.c"
    }
  ]
}