From: Matt Fleming <matt@console-pimps.org>
To: Tejun Heo <tj@kernel.org>
Cc: oleg@redhat.com, vda.linux@googlemail.com,
jan.kratochvil@redhat.com, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
indan@nul.nu, bdonlan@gmail.com, pedro@codesourcery.com
Subject: Re: [PATCH 5/5] ptrace: implement PTRACE_LISTEN
Date: Fri, 23 Sep 2011 12:17:30 +0100 [thread overview]
Message-ID: <1316776650.5262.26.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <1308043218-23619-6-git-send-email-tj@kernel.org>
On Tue, 2011-06-14 at 11:20 +0200, Tejun Heo wrote:
[...]
> + case PTRACE_LISTEN:
> + /*
> + * Listen for events. Tracee must be in STOP. It's not
> + * resumed per-se but is not considered to be in TRACED by
> + * wait(2) or ptrace(2). If an async event (e.g. group
> + * stop state change) happens, tracee will enter STOP trap
> + * again. Alternatively, ptracer can issue INTERRUPT to
> + * finish listening and re-trap tracee into STOP.
> + */
> + if (unlikely(!seized || !lock_task_sighand(child, &flags)))
> + break;
> +
> + si = child->last_siginfo;
> + if (unlikely(!si || si->si_code >> 8 != PTRACE_EVENT_STOP))
> + break;
I've only just noticed this. You really don't want to break out of the
switch while holding sighand->siglock. This should read,
if (unlikely(!si || si->si_code >> 8 != PTRACE_EVENT_STOP)) {
unlock_task_sighand(child, &flags);
break;
}
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-09-23 11:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 9:20 [PATCHSET ptrace] ptrace: implement PTRACE_SEIZE/INTERRUPT and group stop notification, take#5 Tejun Heo
2011-06-14 9:20 ` [PATCH 1/5] job control: introduce JOBCTL_TRAP_STOP and use it for group stop trap Tejun Heo
2011-06-14 9:20 ` [PATCH 2/5] ptrace: implement PTRACE_SEIZE Tejun Heo
2011-06-18 7:55 ` Denys Vlasenko
2011-06-18 7:59 ` Denys Vlasenko
2011-06-18 8:35 ` Tejun Heo
2011-06-18 8:57 ` Denys Vlasenko
2011-06-18 9:04 ` Tejun Heo
2011-06-18 8:30 ` Tejun Heo
2011-06-18 8:58 ` Denys Vlasenko
2011-06-14 9:20 ` [PATCH 3/5] ptrace: implement PTRACE_INTERRUPT Tejun Heo
2011-06-14 9:20 ` [PATCH 4/5] ptrace: implement TRAP_NOTIFY and use it for group stop events Tejun Heo
2011-06-16 19:51 ` Oleg Nesterov
2011-06-17 15:12 ` Tejun Heo
2011-06-17 18:31 ` Oleg Nesterov
2011-06-14 9:20 ` [PATCH 5/5] ptrace: implement PTRACE_LISTEN Tejun Heo
2011-09-23 11:17 ` Matt Fleming [this message]
2011-09-23 12:26 ` Oleg Nesterov
2011-06-16 19:44 ` [PATCHSET ptrace] ptrace: implement PTRACE_SEIZE/INTERRUPT and group stop notification, take#5 Oleg Nesterov
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=1316776650.5262.26.camel@mfleming-mobl1.ger.corp.intel.com \
--to=matt@console-pimps.org \
--cc=akpm@linux-foundation.org \
--cc=bdonlan@gmail.com \
--cc=indan@nul.nu \
--cc=jan.kratochvil@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pedro@codesourcery.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vda.linux@googlemail.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®