linux-kernel - asm-generic/unistd.h and glibc use of NR

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:	Mon, 27 Sep 2010 18:26:29 -0500
From:	Linas Vepstas <linasvepstas@...il.com>
To:	Arnd Bergmann <arnd@...db.de>,
	GLIBC Devel <libc-alpha@...rceware.org>
Cc:	linux-kernel@...r.kernel.org
Subject: asm-generic/unistd.h and glibc use of NR_ipc

I'm trying to figure out the status of glibc w.r.t the latest linux
unistd syscall interface, specifically, the status of the NR_ipc
syscall.   Currently, I see the following:

-- Circa June 2009, Arnd Bergman introduced asm-generic/unistd.h
(into the linux kernel) to provide a generic interface to system
calls. It does *not* define NR_ipc, and instead provides
NR_msgsnd, msgrcv, msgget, msgctl etc. syscalls.

-- Current glibc (2.12.1, as well as the current eglibc) does
not appear to use these new calls anywhere. Instead, glibc
has generic (non-arch-specific) implementations of msgsnd
etc.  that use the old NR_ipc interface (see, e.g.
sysdeps/unix/sysv/linux/msgsnd.c, semget.c, shmdt.c, msgrcv.c,
shmget.c, etc.)

Is someone working on patches to get glibc to use the new
syscall interfaces (for IPC)?  Am I missing something? Seems like
any arch wishing to use asm-generic/unistd.h and get glibc working
gets to break new ground, here ... right?

-- Linas
--
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/