summaryrefslogtreecommitdiffstats
path: root/firmware/vicam
diff options
context:
space:
mode:
authorMichael Neuling <mikey@neuling.org>2013-11-20 16:18:54 +1100
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2013-11-21 10:33:45 +1100
commitc13f20ac48328b05cd3b8c19e31ed6c132b44b42 (patch)
treebdb688a623883a87168ef4760b9523a36d444b04 /firmware/vicam
parent148924f7a282b3acb1f8868ae03c3f76be301d8d (diff)
downloadlinux-c13f20ac48328b05cd3b8c19e31ed6c132b44b42.tar.bz2
powerpc/signals: Mark VSX not saved with small contexts
The VSX MSR bit in the user context indicates if the context contains VSX state. Currently we set this when the process has touched VSX at any stage. Unfortunately, if the user has not provided enough space to save the VSX state, we can't save it but we currently still set the MSR VSX bit. This patch changes this to clear the MSR VSX bit when the user doesn't provide enough space. This indicates that there is no valid VSX state in the user context. This is needed to support get/set/make/swapcontext for applications that use VSX but only provide a small context. For example, getcontext in glibc provides a smaller context since the VSX registers don't need to be saved over the glibc function call. But since the program calling getcontext may have used VSX, the kernel currently says the VSX state is valid when it's not. If the returned context is then used in setcontext (ie. a small context without VSX but with MSR VSX set), the kernel will refuse the context. This situation has been reported by the glibc community. Based on patch from Carlos O'Donell. Tested-by: Haren Myneni <haren@linux.vnet.ibm.com> Signed-off-by: Michael Neuling <mikey@neuling.org> Cc: stable@vger.kernel.org Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'firmware/vicam')
0 files changed, 0 insertions, 0 deletions