Re: [PATCH] Add key management syscalls to non-i386 archs

[Andi Kleen]

David Howells <dhowells@xxxxxxxxxx> writes:
>  /* Syscall protocol:
> diff -uNrp linux-2.6.9-bk4/include/asm-x86_64/unistd.h linux-2.6.9-bk4-keys/include/asm-x86_64/unistd.h
> --- linux-2.6.9-bk4/include/asm-x86_64/unistd.h	2004-10-19 10:42:16.000000000 +0100
> +++ linux-2.6.9-bk4-keys/include/asm-x86_64/unistd.h	2004-10-20 14:06:01.645026869 +0100
> @@ -556,8 +556,14 @@ __SYSCALL(__NR_mq_getsetattr, sys_mq_get
>  __SYSCALL(__NR_kexec_load, sys_ni_syscall)
>  #define __NR_waitid		247
>  __SYSCALL(__NR_waitid, sys_waitid)
> +#define __NR_add_key		248
> +__SYSCALL(__NR_add_key, sys_add_key)

Hey, I already allocated 248 for setaltroot. And no, you cannot
allocate system calls on your own without going through the 
architecture maintainer. The normal workflow is that you add
them to i386 and the other follow on their own.

Andrew, please don't apply the x86-64 parts of this.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/