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: <200805012117.12991.arnd@arndb.de>
Date:	Thu, 1 May 2008 21:17:10 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	John Williams <jwilliams@...e.uq.edu.au>
Cc:	monstr@...nam.cz, microblaze-uclinux@...e.uq.edu.au,
	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,
	John Williams <john.williams@...alogix.com>,
	Stephen Neuendorffer <stephen.neuendorffer@...inx.com>,
	John Linn <John.Linn@...inx.com>
Subject: Re: microblaze syscall list

On Monday 28 April 2008, Arnd Bergmann wrote:
> How about this strategy then:
> * Change all the data types and syscall numbers in the -for-2.6.27
> branch to only include the minimal set, and a modern ABI
> * Add the old interfaces as an out-of-tree patch that adds source
> level compatibility with the old libc, but does not modify any
> of the new interfaces, so that a patched kernel can run all binaries
> built for the upstream version.
> * phase out the old source interface gradually, as all users update
> their libc source code.

Any news on this from the microblaze people? Have you made up your mind
on what route you want to go?

	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/