From: Oleg Nesterov <oleg@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Denys Vlasenko" <vda.linux@googlemail.com>,
"Denys Vlasenko" <dvlasenk@redhat.com>,
linux-kernel@vger.kernel.org,
"Łukasz Michalik" <lmi@ift.uni.wroc.pl>,
"Dmitry V. Levin" <ldv@altlinux.org>
Subject: Re: ptrace fixes for 3.2
Date: Wed, 4 Jan 2012 16:59:27 +0100 [thread overview]
Message-ID: <20120104155927.GB27484@redhat.com> (raw)
In-Reply-To: <20120104153134.GL31746@google.com>
Hello,
On 01/04, Tejun Heo wrote:
>
> On Wed, Jan 04, 2012 at 12:35:34PM +0100, Oleg Nesterov wrote:
> > Can't understand how did we miss this, but WARN_ON_ONCE(!ptrace)
> > in do_signal_stop() is not right. Debugger can resume the stopped
> > task, and it can clone the _untraced_ thread running in the stopped
> > group.
>
> Right, we should be setting JOBCTL_STOP_PENDING for newly cloned tasks
> if sigstop is in effect.
Yes, probably this is the natural choice.
> Looks good to me, provided proper fix is coming soon. :p
Good.
Yes, this is the temporary fix for 3.2.
Thanks!
Oleg.
next prev parent reply other threads:[~2012-01-04 16:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 18:55 Possible bug introduced in commit 9b84cca Denys Vlasenko
2011-12-28 21:07 ` Denys Vlasenko
2011-12-28 21:23 ` Łukasz Michalik
2011-12-29 11:32 ` Oleg Nesterov
2011-12-29 12:05 ` Oleg Nesterov
2012-01-03 14:29 ` Oleg Nesterov
2012-01-03 15:44 ` ptrace fixes for 3.2 Oleg Nesterov
2012-01-03 16:30 ` Tejun Heo
2012-01-03 17:09 ` Oleg Nesterov
2012-01-03 19:18 ` Tejun Heo
2012-01-04 11:35 ` Oleg Nesterov
2012-01-04 15:31 ` Tejun Heo
2012-01-04 15:59 ` Oleg Nesterov [this message]
2012-01-03 16:51 ` Denys Vlasenko
2012-01-04 9:00 ` Łukasz Michalik
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=20120104155927.GB27484@redhat.com \
--to=oleg@redhat.com \
--cc=dvlasenk@redhat.com \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lmi@ift.uni.wroc.pl \
--cc=tj@kernel.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 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.