summaryrefslogtreecommitdiff
path: root/drivers/rtc/class.c
diff options
context:
space:
mode:
authorPhil Carmody <ext-phil.2.carmody@nokia.com>2009-07-24 13:59:17 +0800
committerHerbert Xu <herbert@gondor.apana.org.au>2009-07-24 13:59:17 +0800
commit7b4ffcf953f091a815df081911c5e75c8a38418d (patch)
tree9592ddafb6399806b3e1bbfe86333572ed782e9a /drivers/rtc/class.c
parent0044f3eda9a778ab63c2a5eafede3803f01b0b97 (diff)
downloadlinux-3.10-7b4ffcf953f091a815df081911c5e75c8a38418d.tar.gz
linux-3.10-7b4ffcf953f091a815df081911c5e75c8a38418d.tar.bz2
linux-3.10-7b4ffcf953f091a815df081911c5e75c8a38418d.zip
crypto: aes - Undefined behaviour in crypto_aes_expand_key
It's undefined behaviour in C to write outside the bounds of an array. The key expansion routine takes a shortcut of creating 8 words at a time, but this creates 4 additional words which don't fit in the array. As everyone is hopefully now aware, GCC is at liberty to make any assumptions and optimisations it likes in situations where it can detect that UB has occured, up to and including nasal demons, and as the indices being accessed in the array are trivially calculable, it's rash to invite gcc to do take any liberties at all. Signed-off-by: Phil Carmody <ext-phil.2.carmody@nokia.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/rtc/class.c')
0 files changed, 0 insertions, 0 deletions