From: "Aneesh Kumar K.V" <aneesh.kumar@digital.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Russell King <rmk@arm.linux.org.uk>,
davidm@hpl.hp.com,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: force_successful_syscall_return() buggy?
Date: Tue, 17 Jun 2003 12:24:23 +0530 [thread overview]
Message-ID: <3EEEBB1F.70609@digital.com> (raw)
In-Reply-To: <fa.gvpfoqi.ngk8p2@ifi.uio.no>
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
next parent reply other threads:[~2003-06-17 6:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.it5uct2.s4s8om@ifi.uio.no>
[not found] ` <fa.gvpfoqi.ngk8p2@ifi.uio.no>
2003-06-17 6:54 ` Aneesh Kumar K.V [this message]
2003-06-17 19:01 ` force_successful_syscall_return() buggy? David Mosberger
2003-06-17 18:58 ` David S. Miller
2003-06-19 17:35 ` Richard Henderson
2003-06-15 18:36 Russell King
2003-06-15 23:11 ` Richard Henderson
2003-06-16 2:30 ` Paul Mackerras
2003-06-16 17:38 ` David Mosberger
2003-06-16 17:55 ` Russell King
2003-06-16 18:02 ` David S. Miller
2003-06-16 18:25 ` David Mosberger
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=3EEEBB1F.70609@digital.com \
--to=aneesh.kumar@digital.com \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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