lkml.org 
[lkml]   [2003]   [Jun]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: force_successful_syscall_return() buggy?
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~
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:36    [W:0.054 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site