)]}'
{
  "commit": "9a8d289fbcb7dfd1fc74959e9930b406e76b2002",
  "tree": "d06d101fc0a24619b7b7d8fff2951ac446e7300d",
  "parents": [
    "fbff66108352d19b5cffa7dce26d7638c9dd4d70"
  ],
  "author": {
    "name": "Mimi Zohar",
    "email": "zohar@linux.vnet.ibm.com",
    "time": "Mon Jul 28 07:59:49 2014 -0400"
  },
  "committer": {
    "name": "Mimi Zohar",
    "email": "zohar@linux.vnet.ibm.com",
    "time": "Tue Sep 02 17:03:35 2014 -0400"
  },
  "message": "ima: fix ima_alloc_atfm()\n\nThe patch 3bcced39ea7d: \"ima: use ahash API for file hash\ncalculation\" from Feb 26, 2014, leads to the following static checker\nwarning:\n\nsecurity/integrity/ima/ima_crypto.c:204 ima_alloc_atfm()\n         error: buffer overflow \u0027hash_algo_name\u0027 17 \u003c\u003d 17\n\nUnlike shash tfm memory, which is allocated on initialization, the\nahash tfm memory allocation is deferred until needed.\n\nThis patch fixes the case where ima_ahash_tfm has not yet been\nallocated and the file\u0027s signature/hash xattr contains an invalid hash\nalgorithm.  Although we can not verify the xattr, we still need to\nmeasure the file.  Use the default IMA hash algorithm.\n\nChangelog:\n- set valid algo before testing tfm - based on Dmitry\u0027s comment\n\nReported-by: Dan Carpenter \u003cdan.carpenter@oracle.com\u003e\nSigned-off-by: Mimi Zohar \u003czohar@linux.vnet.ibm.com\u003e\nSigned-off-by: Dmitry Kasatkin \u003cd.kasatkin@samsung.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0bd732843fe70861b0d1bb58bceada6c972f8122",
      "old_mode": 33188,
      "old_path": "security/integrity/ima/ima_crypto.c",
      "new_id": "2d103dc13d907119386017c3c4e645e6157698ff",
      "new_mode": 33188,
      "new_path": "security/integrity/ima/ima_crypto.c"
    }
  ]
}