diff options
author | Michael Neuling <mikey@neuling.org> | 2008-10-23 00:42:36 +0000 |
---|---|---|
committer | Paul Mackerras <paulus@samba.org> | 2008-10-31 16:12:00 +1100 |
commit | 16c29d180becc5bdf92fd0fc7314a44a671b5f4e (patch) | |
tree | cf8ed40be5a456dd6b61eda6d339cd4b8341f655 /drivers/of | |
parent | b160544cccb403310cf38ddb3ebc156ea454848a (diff) | |
download | kernel_samsung_tuna-16c29d180becc5bdf92fd0fc7314a44a671b5f4e.zip kernel_samsung_tuna-16c29d180becc5bdf92fd0fc7314a44a671b5f4e.tar.gz kernel_samsung_tuna-16c29d180becc5bdf92fd0fc7314a44a671b5f4e.tar.bz2 |
powerpc: Fix swapcontext system for VSX + old ucontext size
Since VSX support was added, we now have two sizes of ucontext_t;
the older, smaller size without the extra VSX state, and the new
larger size with the extra VSX state. A program using the
sys_swapcontext system call and supplying smaller ucontext_t
structures will currently get an EINVAL error if the task has
used VSX (e.g. because of calling library code that uses VSX) and
the old_ctx argument is non-NULL (i.e. the program is asking for
its current context to be saved). Thus the program will start
getting EINVAL errors on calls that previously worked.
This commit changes this behaviour so that we don't send an EINVAL in
this case. It will now return the smaller context but the VSX MSR bit
will always be cleared to indicate that the ucontext_t doesn't include
the extra VSX state, even if the task has executed VSX instructions.
Both 32 and 64 bit cases are updated.
[paulus@samba.org - also fix some access_ok() and get_user() calls]
Thanks to Ben Herrenschmidt for noticing this problem.
Signed-off-by: Michael Neuling <mikey@neuling.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'drivers/of')
0 files changed, 0 insertions, 0 deletions