From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Roland McGrath <roland@redhat.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] notify_parent and ptrace cleanup
Date: Thu, 26 Aug 2004 06:45:35 +0900 [thread overview]
Message-ID: <87hdqqlwn4.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <200408252107.i7PL7XWw017681@magilla.sf.frob.com>
> > SIGKILL _already_ doesn't actually wake up a ptraced task. It just informs
> > the tracer, last I looked.
I'm thinking the following issue here,
For example,
ptraced task stopping:
in get_signal_to_deliver(),
set_current_state(TASK_STOPPED);
spin_unlock_irq(¤t->sighand->siglock);
notify_parent(current, SIGCHLD);
schedule();
in here, root want to kill those tasks,
kill -> ... -> specific_send_sig_info -> signal_wake_up(t, sig == SIGKILL)
in signal_wake_up(),
mask = TASK_INTERRUPTIBLE;
if (resume)
mask |= TASK_STOPPED;
if (!wake_up_state(t, mask))
Hmm.. I may be missing something...?
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2004-08-25 21:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 0:40 [PATCH] notify_parent cleanup Roland McGrath
2004-08-18 6:44 ` Andrew Morton
2004-08-21 1:09 ` [PATCH] notify_parent and ptrace cleanup Roland McGrath
2004-08-21 11:47 ` OGAWA Hirofumi
2004-08-25 2:43 ` Roland McGrath
2004-08-25 17:51 ` OGAWA Hirofumi
2004-08-25 18:08 ` Roland McGrath
2004-08-25 19:48 ` OGAWA Hirofumi
2004-08-25 19:54 ` Linus Torvalds
2004-08-25 20:20 ` Roland McGrath
2004-08-25 20:53 ` OGAWA Hirofumi
2004-08-25 21:02 ` Linus Torvalds
2004-08-25 21:07 ` Roland McGrath
2004-08-25 21:45 ` OGAWA Hirofumi [this message]
2004-08-19 4:26 ` [PATCH] notify_parent cleanup OGAWA Hirofumi
2004-08-19 20:59 ` Roland McGrath
2004-08-19 22:01 ` OGAWA Hirofumi
2004-08-19 22:04 ` 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=87hdqqlwn4.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.