summaryrefslogtreecommitdiffstats
path: root/crypto/khazad.c
diff options
context:
space:
mode:
authorUwe Kleine-König <u.kleine-koenig@pengutronix.de>2014-06-03 17:24:51 +0200
committerUwe Kleine-König <u.kleine-koenig@pengutronix.de>2014-07-01 11:12:08 +0200
commit03eca200064381d05a54126a711203d443508d80 (patch)
treef3200b290cba8c9d6a031852a4c11d9045ce5269 /crypto/khazad.c
parent4c834452aad01531db949414f94f817a86348d59 (diff)
downloadlinux-03eca200064381d05a54126a711203d443508d80.tar.bz2
ARM: nommu: don't limit TASK_SIZE
With TASK_SIZE set to the maximal RAM address booting in some XIP configurations fails (e.g. on efm32 DK3750). The problem is that strncpy_from_user et al. check for the address not being above TASK_SIZE (since 8c56cc8be5b3 (ARM: 7449/1: use generic strnlen_user and strncpy_from_user functions)) and this makes booting fail if the XIP flash is above the RAM address space. This change is in line with blackfin, frv and m68k which also use 0xffffffff for TASK_SIZE with !MMU. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Diffstat (limited to 'crypto/khazad.c')
0 files changed, 0 insertions, 0 deletions