From: Richard Henderson <rth@twiddle.net>
To: davidm@hpl.hp.com
Cc: "Aneesh Kumar K.V" <aneesh.kumar@digital.com>,
"David S. Miller" <davem@redhat.com>,
Russell King <rmk@arm.linux.org.uk>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: force_successful_syscall_return() buggy?
Date: Thu, 19 Jun 2003 10:35:47 -0700 [thread overview]
Message-ID: <20030619173547.GA9514@twiddle.net> (raw)
In-Reply-To: <16111.25976.768140.306522@napali.hpl.hp.com>
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~
next prev parent reply other threads:[~2003-06-19 17:22 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 ` force_successful_syscall_return() buggy? Aneesh Kumar K.V
2003-06-17 19:01 ` David Mosberger
2003-06-17 18:58 ` David S. Miller
2003-06-19 17:35 ` Richard Henderson [this message]
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=20030619173547.GA9514@twiddle.net \
--to=rth@twiddle.net \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.