All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: roland@redhat.com, jan.kratochvil@redhat.com,
	vda.linux@googlemail.com, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	indan@nul.nu
Subject: Re: [PATCHSET] ptrace,signal: group stop / ptrace updates, take#2
Date: Mon, 7 Mar 2011 14:03:32 +0100	[thread overview]
Message-ID: <20110307130332.GA10777@redhat.com> (raw)
In-Reply-To: <1299321427-15051-1-git-send-email-tj@kernel.org>

On 03/05, Tejun Heo wrote:
>
> This patchset contains the following ten patches.
>
>  0001-signal-fix-SIGCONT-notification-code.patch
>  0002-ptrace-remove-the-extra-wake_up_state-from-ptrace_de.patch
>  0003-signal-remove-superflous-try_to_freeze-loop-in-do_si.patch
>  0004-ptrace-kill-tracehook_notify_jctl.patch
>  0005-ptrace-add-why-to-ptrace_stop.patch
>  0006-signal-fix-premature-completion-of-group-stop-when-i.patch
>  0007-signal-use-GROUP_STOP_PENDING-to-stop-once-for-a-sin.patch
>  0008-ptrace-participate-in-group-stop-from-ptrace_stop-if.patch
>  0009-ptrace-make-do_signal_stop-use-ptrace_stop-if-the-ta.patch
>  0010-ptrace-clean-transitions-between-TASK_STOPPED-and-TR.patch
>
> In light of the proposal, this patchset can be separated into two
> parts.  The first part, patches 0001 through 0006, tightens various
> loose ends and prepare for further changes.  Except for 0004, every
> patch is acked by Oleg and/or Roland.  0004 doesn't cause any behavior
> change and removes a tracehook for future changes.
>
> The second part, 0007-0010, fixes group stop participation accounting
> and make tracees always stop in TASK_TRACED instead of TASK_STOPPED.
> IOW, it implements "P1. Always TASK_TRACED while ptraced" of the
> proposal.

Looks like, we already discussed these changes? I mean, at first
glance the only difference (compared to the previous series) is that
10/10 simplifies the usage of task_clear_group_stop_trapping().

In this case please free to add my reviewed-by or acked-by.

> Roland, Oleg, Andrew, if there's no objection, I'd like to set up a
> git tree to route further developments in the area.  We're going to
> see a lot of patches and it's simply much more efficient to have a
> dedicated stable git branch.

Agreed.

> I don't really care who controls the tree and don't intend to commit
> any patch without Oleg's Acked-by so it would make most sense for Oleg
> to control the branch but, if Oleg dosnn't want to, I'd be happy to do
> it.  No matter who does it, let's _PLEASE_ establish a stable tree.
>
> This patchset is available in the following git branch.
>
>  git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git ptrace-review

Thanks!

As for "who controls" I do not care too. But I think I should help you
as much as I can. I'll contact you in a few days to discuss this, but
let me repeat once again: whatever you prefer is fine for me.

Oleg.


  parent reply	other threads:[~2011-03-07 13:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-05 10:36 [PATCHSET] ptrace,signal: group stop / ptrace updates, take#2 Tejun Heo
2011-03-05 10:36 ` [PATCH 01/10] signal: fix SIGCONT notification code Tejun Heo
2011-03-05 10:36 ` [PATCH 02/10] ptrace: remove the extra wake_up_state() from ptrace_detach() Tejun Heo
2011-03-05 10:37 ` [PATCH 03/10] signal: remove superflous try_to_freeze() loop in do_signal_stop() Tejun Heo
2011-03-05 10:37 ` [PATCH 04/10] ptrace: kill tracehook_notify_jctl() Tejun Heo
2011-03-05 10:37 ` [PATCH 05/10] ptrace: add @why to ptrace_stop() Tejun Heo
2011-03-05 10:37 ` [PATCH 06/10] signal: fix premature completion of group stop when interfered by ptrace Tejun Heo
2011-03-05 10:37 ` [PATCH 07/10] signal: use GROUP_STOP_PENDING to stop once for a single group stop Tejun Heo
2011-03-05 10:37 ` [PATCH 08/10] ptrace: participate in group stop from ptrace_stop() iff the task is trapping for " Tejun Heo
2011-03-05 10:37 ` [PATCH 09/10] ptrace: make do_signal_stop() use ptrace_stop() if the task is being ptraced Tejun Heo
2011-03-05 10:37 ` [PATCH 10/10] ptrace: clean transitions between TASK_STOPPED and TRACED Tejun Heo
2011-03-07 13:03 ` Oleg Nesterov [this message]
2011-03-07 13:20   ` [PATCHSET] ptrace,signal: group stop / ptrace updates, take#2 Tejun Heo

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=20110307130332.GA10777@redhat.com \
    --to=oleg@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=indan@nul.nu \
    --cc=jan.kratochvil@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.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 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.