Re: force_successful_syscall_return() buggy?

Richard Henderson
2003-06-19T17:22:09Z

On Tue, Jun 17, 2003 at 12:01:12PM -0700, David Mosberger wrote:
> Aneesh> I was facing a simillar problem with ptrace on Alpha (ptrace
> Aneesh> on alpha expect the pt_regs at current + 2*PAGE_SIZE for
> Aneesh> 2.4. kernel ) w.r.t www.openssi.org project. What i found
> Aneesh> was that even after we return to user space subsequent
> Aneesh> syscalls are not putting pt_regs at that offset. I guess
> Aneesh> while entering the kernel kernel stack pointer always point
> Aneesh> to value stored in thread_struct.ksp ?
>
> If a platform doesn't start with an empty kernel stack on entry from
> user-space, that platform will be wasting (precious) stack space and
> ptrace() most likely won't work reliably. Personally, I'd consider
> such behavior a bug...

So would I. It's now fixed.

r~