Re: How should nano_sleep be fixed (was: ptrace(), fork(), sleep(), exit(), SIGCHLD)

• Next message: Paul Clements: "Re: gcc bug causing problem in kernel builds"
• Previous message: Jes Sorensen: "Re: Will 2.6 require Python for any configuration ? (CML2)"
• In reply to: Russell King: "Re: How should nano_sleep be fixed (was: ptrace(), fork(), sleep(), exit(), SIGCHLD)"
• Reply: Russell King: "Re: How should nano_sleep be fixed (was: ptrace(), fork(), sleep(), exit(), SIGCHLD)"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Russell King wrote:
>
> On Fri, Aug 17, 2001 at 12:56:31PM -0700, george anzinger wrote:
> > Uh..? I though that was what I was allowing. It seems to me to be a
> > lot of extra work to put the same code in 15 different archs.
> > Especially if one does not really know each of them, nor can any one
> > group (or individual) be expected to be able to test (or even have the
> > hardware to test) each of them.
>
> Umm, my best advice is to look at sys_fork() and do_fork(), sys_execve()
> and do_execve().
>
Sorry, but none of those system calls requires the registers which is
where the problem is.

George
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Paul Clements: "Re: gcc bug causing problem in kernel builds"
• Previous message: Jes Sorensen: "Re: Will 2.6 require Python for any configuration ? (CML2)"
• In reply to: Russell King: "Re: How should nano_sleep be fixed (was: ptrace(), fork(), sleep(), exit(), SIGCHLD)"
• Reply: Russell King: "Re: How should nano_sleep be fixed (was: ptrace(), fork(), sleep(), exit(), SIGCHLD)"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Aug 23 2001 - 21:01:01 EST