From: "Luming Yu" <luming.yu@gmail.com>
To: "Roland McGrath" <roland@redhat.com>
Cc: "Petr Tesarik" <ptesarik@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org
Subject: Re: [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a race
Date: Tue, 27 May 2008 14:34:26 +0800 [thread overview]
Message-ID: <3877989d0805262334j1ce4d0efhe05e0aa8c3975a28@mail.gmail.com> (raw)
In-Reply-To: <20080527061209.9A24426FAA6@magilla.localdomain>
On Tue, May 27, 2008 at 2:12 PM, Roland McGrath <roland@redhat.com> wrote:
>> [<a00000010000a9f0>] skip_rbs_switch+0xe0/0x110
>> sp=e000000141c9fe30 bsp=e000000141c90cf8
>> [<a000000000010740>] __kernel_syscall_via_break+0x0/0x20
>> sp=e000000141ca0000 bsp=e000000141c90cf8
>> [<a0000001000971c0>] ptrace_stop+0xa0/0x3e0
>> sp=e00000014716fdb0 bsp=e000000147160ca8
>> [<a000000100097650>] ptrace_notify+0x150/0x1c0
>> sp=e00000014716fdb0 bsp=e000000147160c88
>
> If this is a backtrace of a single thread on the same kernel stack, it has
> a stack depth of over 84MB. You still need to follow the path inside
you are right, I just find outputs of two different thread are mixed!
Please just ignore the call trace above..
next prev parent reply other threads:[~2008-05-27 6:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 2:47 Luming Yu
2008-05-22 8:47 ` Petr Tesarik
2008-05-22 9:16 ` Luming Yu
2008-05-22 11:18 ` Roland McGrath
2008-05-22 12:12 ` Petr Tesarik
2008-05-22 20:39 ` Roland McGrath
2008-05-23 12:33 ` Luming Yu
2008-05-22 13:24 ` Luming Yu
2008-05-22 20:34 ` Roland McGrath
2008-05-23 3:42 ` Luming Yu
2008-05-23 4:19 ` Roland McGrath
2008-05-23 5:24 ` Luming Yu
2008-05-26 0:15 ` Roland McGrath
2008-05-26 1:30 ` Luming Yu
2008-05-27 3:31 ` Luming Yu
2008-05-27 4:04 ` Roland McGrath
2008-05-27 5:49 ` Luming Yu
2008-05-27 6:12 ` Roland McGrath
2008-05-27 6:25 ` Petr Tesarik
2008-06-03 6:04 ` Luming Yu
2008-06-03 9:01 ` Petr Tesarik
2008-06-03 14:32 ` Petr Tesarik
2008-06-03 21:01 ` Roland McGrath
2008-06-03 21:31 ` Luck, Tony
2008-06-03 22:13 ` Roland McGrath
2008-06-10 8:23 ` Luming Yu
2008-06-04 2:16 ` Luming Yu
2008-06-04 9:16 ` Petr Tesarik
2008-06-05 1:49 ` Luming Yu
2008-06-05 11:16 ` Petr Tesarik
2008-06-06 0:07 ` Roland McGrath
2008-09-09 3:06 ` Luming Yu
2008-09-10 5:55 ` Roland McGrath
2008-09-16 8:50 ` Luming Yu
2008-09-17 17:01 ` Roland McGrath
2008-09-18 5:44 ` Luming Yu
2008-05-27 6:34 ` Luming Yu [this message]
2008-05-27 8:48 ` Luming Yu
2008-05-28 9:14 ` Luming Yu
2008-06-03 6:02 ` Luming Yu
2008-05-30 8:05 ` Roland McGrath
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=3877989d0805262334j1ce4d0efhe05e0aa8c3975a28@mail.gmail.com \
--to=luming.yu@gmail.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ptesarik@suse.cz \
--cc=roland@redhat.com \
/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®