From: rabin@rab.in (Rabin Vincent)
To: linux-arm-kernel@lists.infradead.org
Subject: SMP: BUG() on cat /proc/$PID/stack
Date: Wed, 19 Jan 2011 22:34:41 +0530 [thread overview]
Message-ID: <20110119165516.GA19356@debian> (raw)
In-Reply-To: <20110113231136.GF24149@n2100.arm.linux.org.uk>
On Thu, Jan 13, 2011 at 11:11:36PM +0000, Russell King - ARM Linux wrote:
> x86 stack walking is very different from ARM unwinding. I'd rather not
> expose the unwinder to a volatile stack - that's probably a recipe for
> it "sometimes" working and other times going oops because the stack
> changed beneath it.
Even on UP, with preemption enabled, isn't there no guarantee that the
target stack won't change beneath us, since the task we're examining can
preempt us?
Don't we need something like the below?
8<------
prev parent reply other threads:[~2011-01-19 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 18:54 SMP: BUG() on cat /proc/$PID/stack Rabin Vincent
2011-01-13 23:11 ` Russell King - ARM Linux
2011-01-15 4:56 ` Rabin Vincent
2011-01-19 17:04 ` Rabin Vincent [this message]
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=20110119165516.GA19356@debian \
--to=rabin@rab.in \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).