From: Stas Sergeev <stsp@aknet.ru>
To: Alexander Nyberg <alexn@telia.com>
Cc: Andrew Morton <akpm@osdl.org>,
torvalds@osdl.org, Mateusz Berezecki <mateuszb@gmail.com>,
linux-kernel@vger.kernel.org, zwane@arm.linux.org.uk
Subject: Re: 2.6.12-rc3 OOPS in vanilla source (once more)
Date: Tue, 03 May 2005 21:20:44 +0400 [thread overview]
Message-ID: <4277B2EC.70605@aknet.ru> (raw)
In-Reply-To: <1115120050.945.39.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
Hello.
Alexander Nyberg wrote:
> So, my solution is to instead of just adjusting esp0 that creates an
> inconsitent state I adjust where the user-space registers are saved with
> -8 bytes.
When I did that offending patch,
I was thinking the following way:
- Do we need to adjust that initial
copy of child regs by the 8 bytes too?
- Well, we need that 8 bytes only
when the "struct pt_regs" is incomplete.
Here we copy the *complete* "struct pt_regs",
so shifting that here makes no sense.
And so I adjusted only esp0 and
nothing else. I think this may
actually still be valid.
> This gives us the wanted extra bytes on the start of the stack
> and esp0 is now correct.
Yes, it is now correct by the mean
that it points to the top of the
"struct pt_regs" on the thread startup.
However, it is not *always* points
to the top of the "struct pt_regs".
This -8 means exactly that esp0 can
also point 8 bytes below the top of
the "struct pt_regs" - that's what
we've seen on a sysenter path, and
that's what used crash either.
So I think using esp0 to locate the
top of the "struct pt_regs" is wrong.
It doesn't always point to the top
of that struct. Sometimes it does,
but sometimes points 8 bytes lower.
IMHO the ptrace.c have to be fixed
instead so to not use this wrong
assumption any more. What do you think?
Btw, I attached the slightly "optimized"
version of your patch (haven't tested).
Just to avoid a few assignments/typecasts.
[-- Attachment #2: process.c.diff --]
[-- Type: text/x-patch, Size: 988 bytes --]
--- process.c.old 2005-05-03 20:15:39.000000000 +0400
+++ process.c 2005-05-03 20:41:25.000000000 +0400
@@ -399,12 +399,6 @@
struct task_struct *tsk;
int err;
- childregs = ((struct pt_regs *) (THREAD_SIZE + (unsigned long) p->thread_info)) - 1;
- *childregs = *regs;
- childregs->eax = 0;
- childregs->esp = esp;
-
- p->thread.esp = (unsigned long) childregs;
/*
* The below -8 is to reserve 8 bytes on top of the ring0 stack.
* This is necessary to guarantee that the entire "struct pt_regs"
@@ -415,7 +409,13 @@
* "struct pt_regs" is possible, but they may contain the
* completely wrong values.
*/
- p->thread.esp0 = (unsigned long) (childregs+1) - 8;
+ childregs = ((struct pt_regs *) (THREAD_SIZE - 8 + (unsigned long)p->thread_info)) - 1;
+ *childregs = *regs;
+ childregs->eax = 0;
+ childregs->esp = esp;
+
+ p->thread.esp = (unsigned long) childregs;
+ p->thread.esp0 = (unsigned long) (childregs+1);
p->thread.eip = (unsigned long) ret_from_fork;
next prev parent reply other threads:[~2005-05-03 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 14:04 2.6.12-rc3 OOPS in vanilla source (once more) Mateusz Berezecki
2005-05-03 3:05 ` Andrew Morton
2005-05-03 11:34 ` Alexander Nyberg
2005-05-03 17:20 ` Stas Sergeev [this message]
2005-05-03 23:45 ` Alexander Nyberg
2005-05-04 3:45 ` Stas Sergeev
2005-05-08 23:12 ` Mateusz Berezecki
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=4277B2EC.70605@aknet.ru \
--to=stsp@aknet.ru \
--cc=akpm@osdl.org \
--cc=alexn@telia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mateuszb@gmail.com \
--cc=torvalds@osdl.org \
--cc=zwane@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