From: Uma shankar <shankar.vk@gmail.com>
To: linux-mm@kvack.org
Subject: accessing stack of non-current task
Date: Tue, 20 Apr 2010 18:08:14 +0530 [thread overview]
Message-ID: <y2t448a67a1004200538l45d46338vcd77b63a0e53d54e@mail.gmail.com> (raw)
Hi,
Is it possible for the kernel to access the user-stack data of a
task different from "current" ? ( This is needed for stack-dump as
well as backtrace. )
I thought the answer is "no". ( Kernel sees memory through the
page-table of "current" )
But I found few places in kernel where this is done. ( eg:
debug_rt_mutex_print_deadlock() in rtmutex-debug.c )
What is the explanation ?
thanks
shankar
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2010-04-20 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 12:38 Uma shankar [this message]
2010-04-20 13:43 ` accessing stack of non-current task Johannes Weiner
2010-04-20 14:00 ` Uma shankar
2010-04-20 17:16 ` Johannes Weiner
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=y2t448a67a1004200538l45d46338vcd77b63a0e53d54e@mail.gmail.com \
--to=shankar.vk@gmail.com \
--cc=linux-mm@kvack.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).