From: Ralf Baechle <ralf@uni-koblenz.de>
To: rth@cygnus.com, Alexander Viro <viro@math.psu.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] show_task() and thread_saved_pc() fix for x86
Date: Sat, 11 Nov 2000 14:06:34 +0100 [thread overview]
Message-ID: <20001111140634.A4865@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.GSO.4.21.0011101618030.17943-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0011101618030.17943-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Fri, Nov 10, 2000 at 04:26:32PM -0500
On Fri, Nov 10, 2000 at 04:26:32PM -0500, Alexander Viro wrote:
> * thread_saved_pc() on x86 returns (thread->esp)[3]. Bogus, since the
> third word from the stack top has absolutely nothing to return address of
> any kind. Correct value: (thread->esp)[0][1] - ebp is on top of the stack
> and the rest is obvious. Current code gives completely bogus addresses -
> try to say Alt-SysRq-T and watch the show.
Reminds me that the Alpha implementation of get_wchan() looks to me like
it doesn't handle all cases of schedule() being called from another
scheduler function correctly. Some Alpha guru may want to take a look at
it.
I recently had to fix the mips / mips64 versions of get_wchan() - for the
dozenth time. I'd really like to see a wchan field in task_struct to avoid
get_wchan breaking every once in a while. Current implementation more than
qualifies as a crazy hack ...
Ralf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-11 23:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 21:26 [PATCH] show_task() and thread_saved_pc() fix for x86 Alexander Viro
2000-11-11 13:06 ` Ralf Baechle [this message]
2000-11-12 10:04 ` Richard Henderson
2000-11-12 2:47 ` Linus Torvalds
2000-11-12 3:18 ` Alexander Viro
2000-11-12 3:23 ` Alexander Viro
2000-11-14 1:50 ` Richard Henderson
2000-11-14 9:19 ` Jean Wolter
2000-11-15 9:38 ` Ralf Baechle
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=20001111140634.A4865@bacchus.dhis.org \
--to=ralf@uni-koblenz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@cygnus.com \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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