diff options
author | Christophe Leroy <christophe.leroy@c-s.fr> | 2016-11-22 11:49:32 +0100 |
---|---|---|
committer | Michael Ellerman <mpe@ellerman.id.au> | 2016-11-23 22:57:20 +1100 |
commit | 902e06eb86cd62753974c249bd1dedae2825b430 (patch) | |
tree | d90f4d8be8f76eabed3ee9fae0cef5d13fc1077f /firmware/yam/9600.bin.ihex | |
parent | 6533b7c16ee5712041b4e324100550e02a9a5dda (diff) | |
download | linux-stable-902e06eb86cd62753974c249bd1dedae2825b430.tar.gz linux-stable-902e06eb86cd62753974c249bd1dedae2825b430.tar.bz2 linux-stable-902e06eb86cd62753974c249bd1dedae2825b430.zip |
powerpc/32: Change the stack protector canary value per task
Partially copied from commit df0698be14c66 ("ARM: stack protector:
change the canary value per task")
A new random value for the canary is stored in the task struct whenever
a new task is forked. This is meant to allow for different canary values
per task. On powerpc, GCC expects the canary value to be found in a global
variable called __stack_chk_guard. So this variable has to be updated
with the value stored in the task struct whenever a task switch occurs.
Because the variable GCC expects is global, this cannot work on SMP
unfortunately. So, on SMP, the same initial canary value is kept
throughout, making this feature a bit less effective although it is still
useful.
Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'firmware/yam/9600.bin.ihex')
0 files changed, 0 insertions, 0 deletions