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

Message-ID: <482017C3.2070508@seznam.cz>
Date:	Tue, 06 May 2008 10:33:07 +0200
From:	Michal Simek <monstr@...nam.cz>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	Arnd Bergmann <arnd@...db.de>, 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

Hi hpa,
>>
>> /* kernel/sys_ni.c */
>>     .long sys_ni_syscall /*  :-)  */
>>
> 
> There is a school of thought that it's useful to reserve a system call
> number (usually zero) as a system call that is *guaranteed* to have no
> effect.

I like your opinion. I'll add it like zero syscall.

Thanks,
M


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