From: Alexey Dobriyan <adobriyan@gmail.com>
To: Ken Chen <kenchen@google.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [patch] add /proc/pid/stack to dump task's stack trace
Date: Thu, 6 Nov 2008 22:51:07 +0300 [thread overview]
Message-ID: <20081106195107.GA17545@x200.localdomain> (raw)
In-Reply-To: <b040c32a0811061101j4a93a0f2pe30c0598726acd08@mail.gmail.com>
On Thu, Nov 06, 2008 at 11:01:39AM -0800, Ken Chen wrote:
> This patch adds the ability to query a task's stack trace via /proc/pid/stack.
> It is considered to be more useful than /proc/pid/wchan as it provides full
> stack trace instead of single depth.
Please, name handler proc_pid_stack following current convention.
And drop space before casts.
> --- a/fs/proc/base.c
> +++ b/fs/proc/base.c
> @@ -338,6 +339,35 @@ static int proc_pid_wchan
> else
> return sprintf(buffer, "%s", symname);
> }
> +
> +#define MAX_STACK_TRACE_DEPTH 32
> +static int proc_stack_trace(struct task_struct *task, char *buffer)
> +{
> + int i, len = 0;
> + unsigned long *entries;
> + struct stack_trace trace;
> +
> + entries = kmalloc(sizeof(*entries) * MAX_STACK_TRACE_DEPTH, GFP_KERNEL);
> + if (!entries)
> + goto out;
> +
> + trace.nr_entries = 0;
> + trace.max_entries = MAX_STACK_TRACE_DEPTH;
> + trace.entries = entries;
> + trace.skip = 0;
> +
> + read_lock(&tasklist_lock);
> + save_stack_trace_tsk(task, &trace);
> + read_unlock(&tasklist_lock);
> +
> + for (i = 0; i < trace.nr_entries; i++) {
> + len += sprintf(buffer + len, "[<%p>] %pS\n",
> + (void *) entries[i], (void *) entries[i]);
> + }
> + kfree(entries);
> +out:
> + return len;
> +}
> #endif /* CONFIG_KALLSYMS */
>
> #ifdef CONFIG_SCHEDSTATS
> @@ -2489,6 +2519,7 @@ static const struct pid_entry tgid_base_stuff[] = {
> DIR("attr", S_IRUGO|S_IXUGO, attr_dir),
> #endif
> #ifdef CONFIG_KALLSYMS
> + INF("stack", S_IRUSR, stack_trace),
> INF("wchan", S_IRUGO, pid_wchan),
> #endif
> #ifdef CONFIG_SCHEDSTATS
next prev parent reply other threads:[~2008-11-06 19:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 19:01 Ken Chen
2008-11-06 19:51 ` Alexey Dobriyan [this message]
2008-11-06 20:12 ` Ken Chen
2008-11-06 20:35 ` Ingo Molnar
2008-11-07 0:30 ` Ken Chen
2008-11-07 0:48 ` Alexey Dobriyan
2008-11-07 7:41 ` Ingo Molnar
2008-11-07 7:59 ` Ingo Molnar
2008-11-07 8:20 ` Alexey Dobriyan
2008-11-07 8:32 ` Ingo Molnar
2008-11-07 8:49 ` Alexey Dobriyan
2008-11-07 8:53 ` Ingo Molnar
2008-11-07 9:03 ` Ingo Molnar
2008-11-07 9:16 ` Andrew Morton
2008-11-07 9:29 ` Ingo Molnar
2008-11-07 17:51 ` Alexey Dobriyan
2008-11-08 12:06 ` Ingo Molnar
2008-11-10 23:54 ` Andrew Morton
2008-11-11 10:00 ` Ingo Molnar
2008-11-11 12:25 ` Marcin Slusarz
2008-11-11 12:33 ` Alexey Dobriyan
2008-11-11 13:20 ` Ingo Molnar
2008-11-11 14:03 ` Mikael Pettersson
2008-11-11 14:19 ` Ingo Molnar
2008-11-07 18:38 ` Ken Chen
2008-11-07 18:46 ` Paul Menage
2008-11-08 12:10 ` Ingo Molnar
2008-11-09 18:08 ` Alexey Dobriyan
2008-11-10 8:41 ` Ingo Molnar
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=20081106195107.GA17545@x200.localdomain \
--to=adobriyan@gmail.com \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®