linux-kernel - Re: [PATCH 5/6] syscalls: add define syscall prefix macro

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:	Mon, 8 Feb 2010 12:54:07 -0500
From:	Christoph Hellwig <hch@...radead.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Jason Baron <jbaron@...hat.com>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	linux-kernel@...r.kernel.org, laijs@...fujitsu.com,
	lizf@...fujitsu.com, rostedt@...dmis.org, fweisbec@...il.com,
	mingo@...e.hu, hpa@...or.com, tglx@...utronix.de,
	mhiramat@...hat.com
Subject: Re: [PATCH 5/6] syscalls: add define syscall prefix macro

On Mon, Feb 08, 2010 at 05:12:36PM +0100, Arnd Bergmann wrote:
> On Monday 08 February 2010, Jason Baron wrote:
> > So I was trying to keep the names of the arch ia32 compat sys calls the
> > same, ie 'sys32_blah'. However, I agree a common naming scheme makes
> > more sense. what about 'arch_compat_sys_blah'? So as to distinguish from
> > the common compat syscalls 'compat_sys_blah'.
> 
> Why do you need to distinguish them? I would hope that we never need to
> have a kernel with both a generic and an arch specific compat version
> of the same syscall.

Well, the usual alignment or number of arguments issues could lead to
just that.  We should deal with it the same way as for native syscalls.

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