Vladimir Murzin 3f4aa45cee ARM: 8226/1: cacheflush: get rid of restarting block ... We cannot restart cacheflush safely if a process provides user-defined signal handler and signal is pending. In this case -EINTR is returned and it is expected that process re-invokes syscall. However, there are a few problems with that: * looks like nobody bothers checking return value from cacheflush * but if it did, we don't provide the restart address for that, so the process has to use the same range again * ...and again, what might lead to looping forever So, remove cacheflush restarting code and terminate cache flushing as early as fatal signal is pending. Cc: stable@vger.kernel.org # 3.12+ Reported-by: Chanho Min <chanho.min@lge.com> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> Acked-by: Will Deacon <will.deacon@arm.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>		2014-11-27 15:55:35 +00:00
..
asm	ARM: 8226/1: cacheflush: get rid of restarting block	2014-11-27 15:55:35 +00:00
debug	Merge tag 'bcm63138-v4' of http://github.com/brcm/linux into next/soc	2014-09-25 23:50:02 +02:00
uapi/asm	ARM: enable bpf syscall	2014-10-29 00:18:20 +00:00