From: Russell King <rmk@arm.linux.org.uk>
To: george anzinger <george@mvista.com>
Cc: "Victor Yodaiken" <yodaiken@fsmlabs.com>,
"christophe barbé" <christophe.barbe@lineo.fr>,
linux-kernel@vger.kernel.org
Subject: Re: How should nano_sleep be fixed (was: ptrace(), fork(), sleep(), exit(), SIGCHLD)
Date: Thu, 23 Aug 2001 21:11:22 +0100 [thread overview]
Message-ID: <20010823211121.H24974@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20010817125727.A16475@hq2> <3B7D76EF.DA34EB23@mvista.com> <20010822194035.K18391@flint.arm.linux.org.uk> <3B8561B9.AC440835@mvista.com>
In-Reply-To: <3B8561B9.AC440835@mvista.com>; from george@mvista.com on Thu, Aug 23, 2001 at 01:04:09PM -0700
On Thu, Aug 23, 2001 at 01:04:09PM -0700, george anzinger wrote:
> Sorry, but none of those system calls requires the registers which is
> where the problem is.
/* Fork a new task - this creates a new program thread.
* This is called indirectly via a small wrapper
*/
asmlinkage int sys_fork(struct pt_regs *regs)
^^^^^^^^^^^^^^^^^^^^
{
return do_fork(SIGCHLD, regs->ARM_sp, regs, 0);
}
/* sys_execve() executes a new program.
* This is called indirectly via a small wrapper
*/
asmlinkage int
sys_execve(char *filenamei, char **argv, char **envp, struct pt_regs *regs)
^^^^^^^^^^^^^^^^^^^^^
{
int error;
char * filename;
filename = getname(filenamei);
error = PTR_ERR(filename);
if (IS_ERR(filename))
goto out;
error = do_execve(filename, argv, envp, regs);
putname(filename);
out:
return error;
}
Certainly looks to me like they do. See the highlighted arguments.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-08-23 20:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 8:29 ptrace(), fork(), sleep(), exit(), SIGCHLD Bruce Janson
2001-08-14 7:28 ` christophe barbé
2001-08-14 15:06 ` Bruce Janson
2001-08-15 15:46 ` george anzinger
2001-08-15 17:53 ` george anzinger
2001-08-15 18:02 ` george anzinger
2001-08-16 0:59 ` How should nano_sleep be fixed (was: ptrace(), fork(), sleep(), exit(), SIGCHLD) george anzinger
2001-08-16 10:17 ` christophe barbé
2001-08-16 10:29 ` Russell King
2001-08-16 14:16 ` george anzinger
2001-08-16 16:00 ` christophe barbé
2001-08-16 16:12 ` Russell King
2001-08-16 18:17 ` george anzinger
2001-08-17 18:25 ` george anzinger
2001-08-17 18:57 ` Victor Yodaiken
2001-08-17 19:56 ` george anzinger
2001-08-22 18:40 ` Russell King
2001-08-23 20:04 ` george anzinger
2001-08-23 20:11 ` Russell King [this message]
2001-08-23 21:13 ` george anzinger
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=20010823211121.H24974@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=christophe.barbe@lineo.fr \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yodaiken@fsmlabs.com \
/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