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]
Date:	Thu, 3 Jan 2013 21:13:03 +0100
From:	Michal Simek <monstr@...str.eu>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	David Howells <dhowells@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	linux-arch@...r.kernel.org
Subject: Re: uapi __NR_syscalls for microblaze

2013/1/3 Arnd Bergmann <arnd@...db.de>:
> On Thursday 03 January 2013, Michal Simek wrote:
>> 2013/1/3 David Howells <dhowells@...hat.com>:
>> > Michal Simek <monstr@...str.eu> wrote:
>> >
>> >> just want to check with you if __NR_syscalls is necessary for user space. I
>> >> see that powerpc and arm have this macro in asm not in uapi like Microblaze.
>> >> If is not needed by user space, I should move it to asm/unistd.h
>> >
>> > It isn't as far as I know...  I recommend putting your question on the
>> > linux-arch mailing list.
>>
>> I have add linux-arch to CC.
>
> Right, I'm pretty sure it's not needed, but it has traditionally been
> exported on a lot of platforms, so you can keep it in UAPI to be
> on the safe side.

Isn't it better to be consistent across all architectures?
If it is wrong to exported and there is no reason to use it in userspace
then all architecture should move it out of uapi.
If there is any reason then it is should be in uapi.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian
--
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/

Powered by blists - more mailing lists