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 05:49:44 +0000 [thread overview]
Message-ID: <3877989d0805262249yab130cbyfc5f5e54065cec5c@mail.gmail.com> (raw)
In-Reply-To: <20080527040454.053C526FA9E@magilla.localdomain>
>
>> It does happen!!
>
> Um. Really? What does happen exactly?
I revised patch a bit, and managed to get this:
Call Trace:
[<a000000100011bd0>] show_stack+0x50/0xa0
spà00000141c9fbb0 bspà00000141c90ea8
[<a000000100011c50>] dump_stack+0x30/0x60
spà00000141c9fd80 bspà00000141c90e90
[<a000000100097a20>] get_signal_to_deliver+0xa0/0x720
spà00000141c9fd80 bspà00000141c90e28
[<a0000001000343d0>] ia64_do_signal+0xb0/0xd00
spà00000141c9fd80 bspà00000141c90d78
[<a000000100012650>] do_notify_resume_user+0xf0/0x140
spà00000141c9fe20 bspà00000141c90d48
[<a00000010000aac0>] notify_resume_user+0x40/0x60
spà00000141c9fe20 bspà00000141c90cf8
[<a00000010000a9f0>] skip_rbs_switch+0xe0/0x110
spà00000141c9fe30 bspà00000141c90cf8
[<a000000000010740>] __kernel_syscall_via_break+0x0/0x20
spà00000141ca0000 bspà00000141c90cf8
[<a0000001000971c0>] ptrace_stop+0xa0/0x3e0
spà0000014716fdb0 bspà00000147160ca8
[<a000000100097650>] ptrace_notify+0x150/0x1c0
spà0000014716fdb0 bspà00000147160c88
[<a00000010002adb0>] syscall_trace+0x30/0xc0
spà0000014716fe30 bspà00000147160c70
[<a00000010002aea0>] syscall_trace_enter+0x60/0xa0
spà0000014716fe30 bspà00000147160c18
[<a00000010000a300>] ia64_trace_syscall+0x40/0x110
spà0000014716fe30 bspà00000147160c18
[<a000000000010740>] __kernel_syscall_via_break+0x0/0x20
spà00000147170000 bspà00000147160c18
next prev parent reply other threads:[~2008-05-27 5:49 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 2:47 [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a race Luming Yu
2008-05-22 8:47 ` [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a Petr Tesarik
2008-05-22 9:16 ` [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a race Luming Yu
2008-05-22 11:18 ` Roland McGrath
2008-05-22 12:12 ` [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a Petr Tesarik
2008-05-22 20:39 ` Roland McGrath
2008-05-23 12:33 ` [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a race 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 [this message]
2008-05-27 6:12 ` Roland McGrath
2008-05-27 6:25 ` [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a Petr Tesarik
2008-06-03 6:04 ` [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a race Luming Yu
2008-06-03 9:01 ` [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a Petr Tesarik
2008-06-03 14:32 ` Petr Tesarik
2008-06-03 21:01 ` Roland McGrath
2008-06-03 21:31 ` [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a race 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 ` [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a Petr Tesarik
2008-06-05 1:49 ` [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a race Luming Yu
2008-06-05 11:16 ` [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a Petr Tesarik
2008-06-06 0:07 ` Roland McGrath
2008-09-09 3:06 ` [RFC PATCH] set TASK_TRACED before arch_ptrace code to fix a race 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
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=3877989d0805262249yab130cbyfc5f5e54065cec5c@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