From: Andrew Morton <akpm@linux-foundation.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Roland McGrath <roland@redhat.com>,
chrisw@sous-sol.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ptrace: ptrace_attach: check PF_KTHREAD + exit_state instead of ->mm
Date: Tue, 5 May 2009 22:03:32 -0700 [thread overview]
Message-ID: <20090505220332.553be936.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090506045613.GB26214@redhat.com>
On Wed, 6 May 2009 06:56:13 +0200 Oleg Nesterov <oleg@redhat.com> wrote:
> > > signals-tracehook_notify_jctl-change.patch
> > > utrace-core.patch
> > > utrace-core-kill-exclude_xtrace-logic.patch
> >
> > I'd swap these three to be after ...
> >
> > > #
> > > ptrace-ptrace_attach-check-pf_kthread-exit_state-instead-of-mm.patch
> > > ptrace-cleanup-check-set-of-pt_ptraced-during-attach.patch
> > > ptrace-do-not-use-task_lock-for-attach.patch
> > > ptrace_get_task_struct-s-tasklist-rcu-make-it-static.patch
>
> Yes, that was the plan.
>
> But, to do this, utrace-core-kill-exclude_xtrace-logic.patch should be
> folded into utrace-core.patch. Otherwise, utrace-core.patch alone can't
> be applied after this new series.
ooooh.
next prev parent reply other threads:[~2009-05-06 5:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 22:47 [PATCH 1/3] ptrace: ptrace_attach: check PF_KTHREAD + exit_state instead of ->mm Oleg Nesterov
2009-05-05 23:47 ` Andrew Morton
2009-05-05 23:57 ` Oleg Nesterov
2009-05-06 1:24 ` Andrew Morton
2009-05-06 2:06 ` Roland McGrath
2009-05-06 4:56 ` Oleg Nesterov
2009-05-06 5:03 ` Andrew Morton [this message]
2009-05-06 7:08 ` Christoph Hellwig
2009-05-06 7:41 ` Ingo Molnar
2009-05-06 2:02 ` Roland McGrath
2009-05-06 4:52 ` Oleg Nesterov
2009-05-07 5:51 ` Roland McGrath
2009-05-09 18:43 ` Oleg Nesterov
2009-05-10 23:11 ` Roland McGrath
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=20090505220332.553be936.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--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.