linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	"Frank Ch. Eigler" <fche@redhat.com>,
	Christoph Hellwig <hch@lst.de>,
	utrace-devel@redhat.com
Subject: Re: tracehooks changes && 2.6.32 -mm merge plans
Date: Thu, 17 Sep 2009 14:56:35 -0700 (PDT)	[thread overview]
Message-ID: <20090917215635.73CE89A5@magilla.sf.frob.com> (raw)
In-Reply-To: Oleg Nesterov's message of  Thursday, 17 September 2009 22:46:56 +0200 <20090917204656.GC29346@redhat.com>

> On 09/15, Andrew Morton wrote:
> >
> > #signals-tracehook_notify_jctl-change.patch: needs changelog folding too
> > signals-tracehook_notify_jctl-change.patch
> > signals-tracehook_notify_jctl-change-do_signal_stop-do-not-call-tracehook_notify_jctl-in-task_stopped-state.patch
> > #signals-introduce-tracehook_finish_jctl-helper.patch: fold into signals-tracehook_notify_jctl-change.patch
> > signals-introduce-tracehook_finish_jctl-helper.patch
> 
> I think these make sense anyway,

Agreed.

> > utrace-core.patch
> >
> >   utrace.  What's happening with this?
> 
> (since Roland didn't reply yet)
> 
> I guess this patch should be updated.

We do have a newer version now with various fixes and clean-ups.
But the current version does not play nice with ptrace (does not
even exclude ptrace any more).  Without at least the ptrace
exclusion, using both utrace modules and ptrace might lead to a
confused kernel or BUG_ON hits.

Past feedback tells us that we need some in-tree users of the
utrace API to get merged too.  Frank was working on such a thing,
and the IBM folks may have another such thing, but I don't know
the present status of those modules.

Oleg is working feverishly on revamping ptrace using utrace.
Other past feedback has suggested this is what people want to see
to justify utrace going in.  That ptrace work is still a bit away
from being ready even for -mm submission.  We're pretty sure that
we will do some more changes in the utrace core to make that work
well, so utrace merged first would be sure to get more changes
later (probably including some API differences).


Thanks,
Roland

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2009-09-18  1:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 23:15 Andrew Morton
2009-09-16  3:46 ` Dmitry Torokhov
2009-09-16  4:14   ` Andrew Morton
2009-09-16  8:33     ` David Härdeman
2009-09-16 15:00     ` Bjorn Helgaas
2009-09-16 20:00       ` Andrew Morton
2009-09-16  7:37 ` memcg merge for 2.6.32 (was Re: 2.6.32 -mm merge plans) Balbir Singh
2009-09-16  7:51   ` Daisuke Nishimura
2009-09-16  7:58   ` KAMEZAWA Hiroyuki
2009-09-16  8:45 ` stack limits [was Re: 2.6.32 -mm merge plans] Pavel Machek
2009-09-16  9:42 ` hwpoison fixes was Re: 2.6.32 -mm merge plans Andi Kleen
2009-09-17 20:15 ` cgrooups && " Oleg Nesterov
2009-09-17 20:38   ` Andrew Morton
2009-09-17 21:08     ` Oleg Nesterov
2009-09-17 20:32 ` do_wait() changes " Oleg Nesterov
2009-09-17 20:46 ` tracehooks " Oleg Nesterov
2009-09-17 21:56   ` Roland McGrath [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=20090917215635.73CE89A5@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=fche@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=oleg@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