public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Björn Steinbrink" <B.Steinbrink@gmx.de>,
	"Russell King" <rmk+lkml@arm.linux.org.uk>,
	"Andrew Morton" <akpm@osdl.org>,
	rusty@rustcorp.com.au, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org
Subject: Re: [PATCH] introduce kernel_execve function to replace __KERNEL_SYSCALLS__
Date: Mon, 21 Aug 2006 10:36:46 +1000	[thread overview]
Message-ID: <17641.30.670343.779791@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <200608201913.39989.arnd@arndb.de>

Arnd Bergmann writes:

> Iit turned out most of the architectures that already implement
> their own execve() call instead of using the _syscall3 function
> for it end up passing the return value of sys_execve down, 
> instead of setting errno.

I really don't like having an "errno" variable in the kernel.  What if
two processes are doing an execve concurrently?

Anyway, your patch returns the (positive) errno value here:

> +	WARN_ON(segment_eq(fs, USER_DS));
> +	ret = execve(filename, (char **)argv, (char **)envp);
> +	if (ret)
> +		ret = errno;
> +
> +	return ret;

but here we are testing for a negative value to mean error:

> -	if (execve("/sbin/shutdown", argv, envp) < 0) {
> +	if (kernel_execve("/sbin/shutdown", argv, envp) < 0) {

Paul.

  parent reply	other threads:[~2006-08-21  0:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060819073031.GA25711@atjola.homenet>
     [not found] ` <200608201501.29296.arnd@arndb.de>
     [not found]   ` <20060820134745.GA11843@atjola.homenet>
2006-08-20 17:13     ` [PATCH] introduce kernel_execve function to replace __KERNEL_SYSCALLS__ Arnd Bergmann
2006-08-20 17:36       ` Chase Venters
2006-08-20 18:25         ` Andrew Morton
2006-08-20 18:32           ` Chase Venters
2006-08-20 19:45             ` Björn Steinbrink
2006-08-20 19:50               ` Arjan van de Ven
2006-08-20 20:11                 ` Björn Steinbrink
2006-08-20 20:20                   ` Arjan van de Ven
2006-08-20 20:36                     ` Björn Steinbrink
2006-08-20 20:40                       ` Arjan van de Ven
2006-08-21  1:55                       ` Jeff Dike
2006-08-20 20:33                   ` Arnd Bergmann
2006-08-20 19:31         ` Arnd Bergmann
2006-08-21  0:36       ` Paul Mackerras [this message]
2006-08-21 15:12         ` Arnd Bergmann
2006-08-21 15:17           ` Russell King
2006-08-22  7:29           ` Benjamin Herrenschmidt
2006-08-22  8:00             ` Björn Steinbrink
2006-08-22 10:06               ` Arnd Bergmann
2006-08-22 13:39                 ` Jeff Dike
2006-08-22 15:13                   ` Arnd Bergmann
2006-08-22 15:37                     ` Jeff Dike

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17641.30.670343.779791@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=B.Steinbrink@gmx.de \
    --cc=akpm@osdl.org \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=rusty@rustcorp.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox