)]}'
{
  "commit": "7b4ffcf953f091a815df081911c5e75c8a38418d",
  "tree": "9592ddafb6399806b3e1bbfe86333572ed782e9a",
  "parents": [
    "0044f3eda9a778ab63c2a5eafede3803f01b0b97"
  ],
  "author": {
    "name": "Phil Carmody",
    "email": "ext-phil.2.carmody@nokia.com",
    "time": "Fri Jul 24 13:59:17 2009 +0800"
  },
  "committer": {
    "name": "Herbert Xu",
    "email": "herbert@gondor.apana.org.au",
    "time": "Fri Jul 24 13:59:17 2009 +0800"
  },
  "message": "crypto: aes - Undefined behaviour in crypto_aes_expand_key\n\nIt\u0027s undefined behaviour in C to write outside the bounds of an array.\nThe key expansion routine takes a shortcut of creating 8 words at a\ntime, but this creates 4 additional words which don\u0027t fit in the array.\n\nAs everyone is hopefully now aware, GCC is at liberty to make any\nassumptions and optimisations it likes in situations where it can\ndetect that UB has occured, up to and including nasal demons, and\nas the indices being accessed in the array are trivially calculable,\nit\u0027s rash to invite gcc to do take any liberties at all.\n\nSigned-off-by: Phil Carmody \u003cext-phil.2.carmody@nokia.com\u003e\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b8b66ec3883b74d8ea2b7b41f1298a4b01a32ca8",
      "old_mode": 33188,
      "old_path": "crypto/aes_generic.c",
      "new_id": "e78b7ee44a7453039938fe772e52e2a1768d90ba",
      "new_mode": 33188,
      "new_path": "crypto/aes_generic.c"
    }
  ]
}