diff options
author | Will Deacon <will.deacon@arm.com> | 2012-05-15 15:51:54 +0100 |
---|---|---|
committer | Russell King <rmk+kernel@arm.linux.org.uk> | 2012-05-17 14:48:56 +0100 |
commit | 56cb248428ead13a6b423ed3f3cf9e4aa01244b1 (patch) | |
tree | bd1ab001b446712e5741220d80ce8c877b9e6482 /arch/arm/mm | |
parent | 1a3abcf41f13666d4ed241c8cc7f48bd38e7b543 (diff) | |
download | linux-3.10-56cb248428ead13a6b423ed3f3cf9e4aa01244b1.tar.gz linux-3.10-56cb248428ead13a6b423ed3f3cf9e4aa01244b1.tar.bz2 linux-3.10-56cb248428ead13a6b423ed3f3cf9e4aa01244b1.zip |
ARM: 7419/1: vfp: fix VFP flushing regression on sigreturn path
Commit ff9a184c ("ARM: 7400/1: vfp: clear fpscr length and stride bits
on entry to sig handler") flushes the VFP state prior to entering a
signal handler so that a VFP operation inside the handler will trap and
force a restore of ABI-compliant registers. Reflushing and disabling VFP
on the sigreturn path is predicated on the saved thread state indicating
that VFP was used by the handler -- however for SMP platforms this is
only set on context-switch, making the check unreliable and causing VFP
register corruption in userspace since the register values are not
necessarily those restored from the sigframe.
This patch unconditionally flushes the VFP state after a signal handler.
Since we already perform the flush before the handler and the flushing
itself happens lazily, the redundant flush when VFP is not used by the
handler is essentially a nop.
Reported-by: Jon Medhurst <tixy@linaro.org>
Signed-off-by: Jon Medhurst <tixy@linaro.org>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'arch/arm/mm')
0 files changed, 0 insertions, 0 deletions