From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] get_wchan on running task sometimes MCAs the machine.
Date: Thu, 17 May 2007 11:38:59 +0000 [thread overview]
Message-ID: <8976.1179401939@ocs3.ocs.com.au> (raw)
In-Reply-To: <20070517111651.GA760@lnx-holt.americas.sgi.com>
Robin Holt (on Thu, 17 May 2007 06:16:52 -0500) wrote:
>Make ia64's get_wchan safer by not unwinding a running tasks stack.
>...
>All that said, I have put together the following simple patch stolen
>directly from i386's get_wchan. If the task is running, why even try.
>
>
>Index: linux-tot-20070517/arch/ia64/kernel/process.c
>=================================>--- linux-tot-20070517.orig/arch/ia64/kernel/process.c 2007-05-17 05:39:54.000000000 -0500
>+++ linux-tot-20070517/arch/ia64/kernel/process.c 2007-05-17 05:44:26.820535382 -0500
>@@ -763,6 +763,9 @@ get_wchan (struct task_struct *p)
> unsigned long ip;
> int count = 0;
>
>+ if (!p || p = current || p->state = TASK_RUNNING)
>+ return 0;
>+
> /*
> * Note: p may not be a blocked task (it could be current or
> * another process running on some other CPU. Rather than
AFAICT there is no lock on struct task_struct p that stops it being
scheduled to run after you test if it is running. proc_task_lookup()
only does get_task_struct() which prevents the task from being deleted,
it does not prevent the task from being scheduled while you are looking
at it.
So even with that check, it can race between not running and running
while you do the unwind, and still get the MCA.
next prev parent reply other threads:[~2007-05-17 11:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 11:16 [PATCH] get_wchan on running task sometimes MCAs the machine Robin Holt
2007-05-17 11:38 ` Keith Owens [this message]
2007-05-17 13:00 ` Robin Holt
2007-05-17 13:05 ` Keith Owens
2007-05-17 14:16 ` David Mosberger-Tang
2007-05-18 3:02 ` Robin Holt
2007-05-18 18:23 ` David Mosberger-Tang
2007-05-18 18:35 ` Robin Holt
2007-05-18 23:01 ` Luck, Tony
2007-05-19 2:08 ` Robin Holt
2007-05-19 2:26 ` David Mosberger-Tang
2007-05-23 3:32 ` Nick Piggin
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=8976.1179401939@ocs3.ocs.com.au \
--to=kaos@sgi.com \
--cc=linux-ia64@vger.kernel.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