All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
	roland@redhat.com
Subject: Re: + signals-tracehook_notify_jctl-change.patch added to -mm tree
Date: Wed, 1 Apr 2009 20:22:24 +0200	[thread overview]
Message-ID: <20090401182224.GA14720@redhat.com> (raw)
In-Reply-To: <20090401123634.GI12966@elte.hu>

On 04/01, Ingo Molnar wrote:
>
> * akpm@linux-foundation.org <akpm@linux-foundation.org> wrote:
>
> > Subject: signals: tracehook_notify_jctl change
> > From: Roland McGrath <roland@redhat.com>
> >
> > This changes tracehook_notify_jctl() so it's called with the siglock held,
> > and changes its argument and return value definition.  These clean-ups
> > make it a better fit for what new tracing hooks need to check.
> >
> > Tracing needs the siglock here, held from the time TASK_STOPPED was set,
> > to avoid potential SIGCONT races if it wants to allow any blocking in its
> > tracing hooks.
> >
> > This also folds the finish_stop() function into its caller
> > do_signal_stop().  The function is short, called only once and only
> > unconditionally.  It aids readability to fold it in.
> >
> > Signed-off-by: Roland McGrath <roland@redhat.com>
> > Cc: Oleg Nesterov <oleg@redhat.com>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>
> Roland: as i have asked you before, i'd like to see explicit Ack's
> from Oleg for all ptrace patches you submit.

I agree with Roland's patch.

In my opinion, we can simplify utrace_report_jctl() a bit, but this
requires more changes in kernel/signal.c, we can do this later.

Acked-by: Oleg Nesterov <oleg@redhat.com>


      reply	other threads:[~2009-04-01 18:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30 22:18 + signals-tracehook_notify_jctl-change.patch added to -mm tree akpm
2009-04-01 12:36 ` Ingo Molnar
2009-04-01 18:22   ` Oleg Nesterov [this message]

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=20090401182224.GA14720@redhat.com \
    --to=oleg@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mm-commits@vger.kernel.org \
    --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 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.