linux-kernel - Syscall wrappers breaks things.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 20 Feb 2009 10:48:58 -0800
From:	David Daney <ddaney@...iumnetworks.com>
To:	Heiko Carstens <heiko.carstens@...ibm.com>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	Ralf Baechle <ralf@...ux-mips.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Syscall wrappers breaks things.

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/