Fix it a bit (after some cross checking with "man arch_prctl"). There were:
*) typos FS/GS and back
*) FS in place of FS_BASE (and the same for GS)
*) the procedure used put_user on &addr, where addr was the parameter (i.e.
changed its param with put_user, completely useless) rather than interpreting
addr as a pointer, as requested in this case (see the man page).
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <[EMAIL PROTECTED]>
---
linux-2.6.11-paolo/arch/um/sys-x86_64/syscalls.c | 16 ++++++++++------
1 files changed, 10 insertions(+), 6 deletions(-)
diff -puN arch/um/sys-x86_64/syscalls.c~uml-fixlet-arch-prctl
arch/um/sys-x86_64/syscalls.c
--- linux-2.6.11/arch/um/sys-x86_64/syscalls.c~uml-fixlet-arch-prctl
2005-03-10 17:25:56.000000000 +0100
+++ linux-2.6.11-paolo/arch/um/sys-x86_64/syscalls.c 2005-03-10
17:32:05.000000000 +0100
@@ -129,23 +129,27 @@ static long arch_prctl_tt(int code, unsi
#ifdef CONFIG_MODE_SKAS
+/* XXX: Must also call arch_prctl in the host, beside saving the segment
bases! */
static long arch_prctl_skas(int code, unsigned long addr)
{
long ret = 0;
switch(code){
- case ARCH_SET_GS:
- current->thread.regs.regs.skas.regs[GS_BASE / sizeof(unsigned
long)] = addr;
- break;
case ARCH_SET_FS:
current->thread.regs.regs.skas.regs[FS_BASE / sizeof(unsigned
long)] = addr;
break;
+ case ARCH_SET_GS:
+ current->thread.regs.regs.skas.regs[GS_BASE / sizeof(unsigned
long)] = addr;
+ break;
case ARCH_GET_FS:
- ret = put_user(current->thread.regs.regs.skas.regs[GS /
sizeof(unsigned long)], &addr);
+ ret = put_user(current->thread.regs.regs.skas.regs[
+ FS_BASE / sizeof(unsigned long)],
+ (unsigned long __user *)addr);
break;
case ARCH_GET_GS:
- ret = put_user(current->thread.regs.regs.skas.regs[FS /
sizeof(unsigned \
-long)], &addr);
+ ret = put_user(current->thread.regs.regs.skas.regs[
+ GS_BASE / sizeof(unsigned long)],
+ (unsigned long __user *)addr);
break;
default:
ret = -EINVAL;
_
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
