diff options
author | Felipe Rechia <felipe.rechia@datacom.com.br> | 2018-10-24 16:57:22 +0300 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-12-01 11:13:47 +0300 |
commit | 88b0950ca323a7b18b6337beb0a028b7458c06f9 (patch) | |
tree | 589bdf72407ab69be0571730fb6e90cf70d24e95 /arch/sparc/include | |
parent | 8ba716e81648b2a0ffe016d2cad74d795ba399cd (diff) | |
download | linux-88b0950ca323a7b18b6337beb0a028b7458c06f9.tar.xz |
powerpc/process: Fix flush_all_to_thread for SPE
[ Upstream commit e901378578c62202594cba0f6c076f3df365ec91 ]
Fix a bug introduced by the creation of flush_all_to_thread() for
processors that have SPE (Signal Processing Engine) and use it to
compute floating-point operations.
>From userspace perspective, the problem was seen in attempts of
computing floating-point operations which should generate exceptions.
For example:
fork();
float x = 0.0 / 0.0;
isnan(x); // forked process returns False (should be True)
The operation above also should always cause the SPEFSCR FINV bit to
be set. However, the SPE floating-point exceptions were turned off
after a fork().
Kernel versions prior to the bug used flush_spe_to_thread(), which
first saves SPEFSCR register values in tsk->thread and then calls
giveup_spe(tsk).
After commit 579e633e764e, the save_all() function was called first
to giveup_spe(), and then the SPEFSCR register values were saved in
tsk->thread. This would save the SPEFSCR register values after
disabling SPE for that thread, causing the bug described above.
Fixes 579e633e764e ("powerpc: create flush_all_to_thread()")
Signed-off-by: Felipe Rechia <felipe.rechia@datacom.com.br>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'arch/sparc/include')
0 files changed, 0 insertions, 0 deletions