linux-kernel - Re: [microblaze-uclinux] 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: <4811A623.80104@itee.uq.edu.au>
Date:	Fri, 25 Apr 2008 19:36:35 +1000
From:	John Williams <jwilliams@...e.uq.edu.au>
To:	microblaze-uclinux@...e.uq.edu.au
CC:	Arnd Bergmann <arnd@...db.de>, Will Newton <will.newton@...il.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	linux-arch@...r.kernel.org, git@...inx.com
Subject: Re: [microblaze-uclinux] Re: microblaze syscall list

Hi Michal, Arnd,

Michal Simek wrote:

>>> 	.long sys_read
>>> 	.long sys_write
>>> 	.long sys_open			/* 5 */
>> Since we have all the new sys_*at calls like openat, we don't really
>> need the old versions any more. The kernel implementation of sys_open
>> basically calls openat. You could do the same in libc instead.
>> Don't know if that's worth it though, opinions?
> 
> I looked at it and there are the different arguments for open and openat
> syscalls. Implementation is almost the same. I keep it now.

Please remember that MicroBlaze has been around as an arch for > 4 
years, just not in the kernel.org tree.  These older style syscall 
interfaces are all part of the uClibc and glibc ports for MicroBlaze.

While I understand that there are shiny new ways of doing all this 
stuff, please don't break our C libraries, toolchains and all else.  A 
MicroBlaze arch in kernel.org that isn't actually supported by a C 
library or toolchain is not much use either!

Can we compromise and say that the new syscall interfaces will be added 
if they are currently missing, but older interfaces retained until the 
libs and toolchains catch up?

John

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