linux-kernel - Re: microblaze syscall list

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200805032314.24669.arnd@arndb.de>
Date:	Sat, 3 May 2008 23:14:23 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Ulrich Drepper <drepper@...hat.com>
Cc:	John Williams <john.williams@...alogix.com>, monstr@...nam.cz,
	Matthew Wilcox <matthew@....cx>,
	Will Newton <will.newton@...il.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	linux-arch@...r.kernel.org, git@...inx.com,
	Stephen Neuendorffer <stephen.neuendorffer@...inx.com>,
	John Linn <John.Linn@...inx.com>
Subject: Re: microblaze syscall list

On Saturday 03 May 2008, Ulrich Drepper wrote:
> Yes, this is how it should be.  It's not done because no architecture
> glibc officially supports arrived after these and similar syscalls
> arrived.  There is no need to implement the not-*at interface, no need
> to implement the creat syscall, etc etc.

Ah, good! So where should the glibc implementation for these calls go?
In the microblaze (and any future architecture) specific source directories,
to be consolidated when you get more of them, or in the common places like
sysdeps/unix/sysv/linux/*.c, with the appropriate #ifndef?

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