From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: roland@redhat.com, utrace-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] introduce tracehook_finish_jctl() helper
Date: Thu, 30 Jul 2009 18:30:35 +0200 [thread overview]
Message-ID: <20090730163035.GA3617@redhat.com> (raw)
In-Reply-To: <20090729155007.f4f5a793.akpm@linux-foundation.org>
On 07/29, Andrew Morton wrote:
>
> On Wed, 29 Jul 2009 04:01:40 +0200
> Oleg Nesterov <oleg@redhat.com> wrote:
>
> > +static inline void tracehook_finish_jctl(void)
> > +{
> > +}
> > +
> > #define DEATH_REAP -1
> > #define DEATH_DELAYED_GROUP_LEADER -2
> >
> > --- __UTRACE/kernel/signal.c~2_FINISH_JCTL 2009-07-29 03:17:49.000000000 +0200
> > +++ __UTRACE/kernel/signal.c 2009-07-29 03:57:07.000000000 +0200
> > @@ -1735,12 +1735,12 @@ static int do_signal_stop(int signr)
> > read_unlock(&tasklist_lock);
> > }
> >
> > + /* Now we don't run again until woken by SIGCONT or SIGKILL */
> > do {
> > schedule();
> > } while (try_to_freeze());
> > - /*
> > - * Now we don't run again until continued.
> > - */
> > +
> > + tracehook_finish_jctl();
> > current->exit_code = 0;
> >
>
> Confused. This patch has no effect.
Yes, currently tracehook_finish_jctl() does nothing. This patch is
needed to add the functional changes later, without touching the code
outside of tracehook/etc. It is like tracehook_notify_resume() which
does nothing until we add the real tracing.
Oleg.
next prev parent reply other threads:[~2009-07-30 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 2:01 [PATCH -mm] introduce tracehook_finish_jctl() helper Oleg Nesterov
2009-07-29 22:45 ` Roland McGrath
2009-07-29 22:50 ` Andrew Morton
2009-07-30 16:30 ` Oleg Nesterov [this message]
2009-08-01 23:32 ` Roland McGrath
2009-08-03 23:53 ` 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=20090730163035.GA3617@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=utrace-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox