![]() | ||||||||||
Messages in this thread |
David S. Miller wrote: > On Mon, 2003-06-16 at 10:55, Russell King wrote:> >>I'm not actually talking about subsequent syscalls issued by the kernel. >>I'm talking about stuff like init, bash, and the module tools.> > > Wrong, after the go for the first time into user space, the > next trap into the kernel will put the pt_regs at the top at > the stack where we expect it to be.> I was facing a simillar problem with ptrace on Alpha (ptrace on alpha expect the pt_regs at current + 2*PAGE_SIZE for 2.4. kernel ) w.r.t www.openssi.org project. What i found was that even after we return to user space subsequent syscalls are not putting pt_regs at that offset. I guess while entering the kernel kernel stack pointer always point to value stored in thread_struct.ksp ? -aneesh - 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 12:36 [from the cache] ©2003-2008 | ||||||||||