Syscall wrappers breaks things.

From: David Daney
Date: Fri Feb 20 2009 - 13:50:33 EST


In commit ee6a093222549ac0c72cfd296c69fa5e7d6daa34 the syscall wrappers infrastructure was introduced.

A typical definition is something like this (from Ralf's patch):

SYSCALL_DEFINE6(32_ipc, u32, call, long, first, long, second, long, third,
unsigned long, ptr, unsigned long, fifth)
{
.
.
.

This creates a symbol sys_32_ipc. The old name of the symbol is sys32_ipc (note the change in the number of '_').

For the mips64 kernel the syscall table for o32 ABI executable contains:

.
.
.
PTR sys32_ipc
.
.
.

This is now linked to the sys32_ipc function in kernel/sys_ni.c which kindly returns ENOSYS.

The long and short of the problem is that the is now a kernel wide mismatch in function names between the names created by SYSCALL_DEFINE*, the syscall tables and kernel/sys_ni.c.

I am not sure what the best solution is, but something should probably be done to un-break things.

Thanks,
David Daney
--
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/