linux-kernel - Re: [PATCH 2/7] rename the provided execve functions to kernel

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: <200608280944.21819.arnd@arndb.de>
Date:	Mon, 28 Aug 2006 09:44:21 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	"Randy.Dunlap" <rdunlap@...otime.net>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	Jeff Dike <jdike@...toit.com>,
	Bjoern Steinbrink <B.Steinbrink@....de>,
	Arjan van de Ven <arjan@...radead.org>,
	Chase Venters <chase.venters@...entec.com>,
	Andrew Morton <akpm@...l.org>,
	Russell King <rmk+lkml@....linux.org.uk>, rusty@...tcorp.com.au
Subject: Re: [PATCH 2/7] rename the provided execve functions to kernel_execve

On Monday 28 August 2006 04:20, Randy.Dunlap wrote:
> Question:
> All other syscalls (in syscalls.h) return long or unsigned long
> or ssize_t etc.  I.e., none of them return int.  Does this one
> return int because it's strictly an inside-the-kernel "syscall",
> not exposed to userspace?

Well, it's not really a system call in the first place, but
I could not find any other place where it would fit.
The prototype of the kernel_execve function is the one from
the man execve page, and also similar to those that were
generated by the _syscall3() macro before.

	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/