diff options
| author | David Howells <dhowells@redhat.com> | 2012-05-11 10:56:56 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-06-01 15:12:54 +0800 |
| commit | 5032d5a70bf303543fef56d014a2b69f70d5714c (patch) | |
| tree | 11a7b4116520f84ea1b3db9b749c3f15f67ce577 /security | |
| parent | 77f38874d05fef08ca1182155bd823f06343a3ad (diff) | |
| download | kernel_samsung_smdk4412-5032d5a70bf303543fef56d014a2b69f70d5714c.zip kernel_samsung_smdk4412-5032d5a70bf303543fef56d014a2b69f70d5714c.tar.gz kernel_samsung_smdk4412-5032d5a70bf303543fef56d014a2b69f70d5714c.tar.bz2 | |
KEYS: Use the compat keyctl() syscall wrapper on Sparc64 for Sparc32 compat
commit 45de6767dc51358a188f75dc4ad9dfddb7fb9480 upstream.
Use the 32-bit compat keyctl() syscall wrapper on Sparc64 for Sparc32 binary
compatibility.
Without this, keyctl(KEYCTL_INSTANTIATE_IOV) is liable to malfunction as it
uses an iovec array read from userspace - though the kernel should survive this
as it checks pointers and sizes anyway.
I think all the other keyctl() function should just work, provided (a) the top
32-bits of each 64-bit argument register are cleared prior to invoking the
syscall routine, and the 32-bit address space is right at the 0-end of the
64-bit address space. Most of the arguments are 32-bit anyway, and so for
those clearing is not required.
Signed-off-by: David Howells <dhowells@redhat.com
cc: "David S. Miller" <davem@davemloft.net>
cc: sparclinux@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions