public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Roland McGrath <roland@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	utrace-devel@redhat.com, linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	Oleg Nesterov <oleg@redhat.com>,
	Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: [PATCH 3/3] utrace-based ftrace "process" engine, v2
Date: Sun, 22 Mar 2009 13:37:49 +0100	[thread overview]
Message-ID: <20090322123749.GF19826@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.00.0903211501060.3030@localhost.localdomain>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Sat, 21 Mar 2009, Frank Ch. Eigler wrote:
> > 
> > > If testing utrace against its main application requires installation
> > > of a complete enterprise distro from a distro [...]
> > 
> > This has *never* been a requirement.
> 
> You guys are getting off a tangent.
> 
> Let's go back to the post that started this all.
> 
> > The thing is, utrace crashes in Fedora have dominated kerneloops.org 
> > for many months, so i'm not sure what to make of the idea of posting 
> > a 4000+ lines of core kernel code patchset on the last day of the 
> > development cycle, a posting that has carefully avoided the Cc:-ing 
> > of affected maintainers ;-)
> 
> .. and dammit, I agree 100%. If utrace really shows up in _any_ 
> way on kerneloops.org, then I think THE ENTIRE DISCUSSION in this 
> thread is moot.
> 
> I'm not going to take known-bad crap. It's that simple. Don't 
> bother posting it, don't bother discussing it, don't bother making 
> excuses for it.

The kerneloops stats on utrace crashes are way down currently,
after that peak last fall. So i didnt want to suggest that it's 
known-broken now - i only wanted to point out that it's a 
known-risky area and that the submission of it should involve
the affected maintainers/developers.

Regarding current stability, Roland, Frank, is the utrace patch in 
latest (today's) Fedora rawhide:

 -rw-r--r-- 1 root root 176555 2009-01-08 05:42 linux-2.6-utrace.patch

a bug fixed equivalent of the utrace bits that crashed in the 
2.6.26.3 kernel? In that case it is certainly known-good.

Or is it a slimmed-down version?

The ptrace bits and signoffs from Oleg and Alexey would certainly 
help (me) in trusting it. (I've Cc:-ed Oleg and Alexey)

The ftrace bits could certainly be staged to go in via the tracing 
tree (in .31 or so) after the utrace-core+ptrace bits went upstream.

	Ingo

  parent reply	other threads:[~2009-03-22 12:38 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-21  1:39 [PATCH 0/3] utrace Roland McGrath
2009-03-21  1:41 ` [PATCH 1/3] signals: tracehook_notify_jctl change Roland McGrath
2009-03-21  1:41 ` [PATCH 2/3] utrace core Roland McGrath
2009-03-21  8:49   ` Andrew Morton
2009-03-21 14:08     ` Renzo Davoli
2009-03-21 14:34       ` Ingo Molnar
2009-03-21 16:37         ` Renzo Davoli
2009-03-21 16:44           ` Ingo Molnar
2009-03-23  4:34             ` Roland McGrath
2009-03-23  4:35     ` Roland McGrath
2009-03-23 10:57     ` Will Newton
2009-03-21  1:42 ` [PATCH 3/3] utrace-based ftrace "process" engine, v2 Roland McGrath
2009-03-21  7:43   ` Ingo Molnar
2009-03-21  8:39     ` Andrew Morton
2009-03-21  9:12       ` Ingo Molnar
2009-03-21 11:19         ` Andrew Morton
2009-03-21 11:51           ` Frank Ch. Eigler
2009-03-21 12:04             ` Andrew Morton
2009-03-21 12:57               ` Frank Ch. Eigler
2009-03-21 15:45               ` Ingo Molnar
2009-03-21 20:35                 ` Diego Calleja
2009-03-22 12:17                   ` Ingo Molnar
2009-03-21 21:34                 ` Andrew Morton
2009-03-21 21:51                   ` Frank Ch. Eigler
2009-03-21 22:02                     ` Linus Torvalds
2009-03-21 22:20                       ` Frank Ch. Eigler
2009-03-21 22:37                         ` Alexey Dobriyan
2009-03-21 23:38                           ` Frank Ch. Eigler
2009-03-22 10:25                             ` Ingo Molnar
2009-03-23  5:33                               ` Roland McGrath
2009-03-23  5:20                             ` Roland McGrath
2009-03-22 12:37                       ` Ingo Molnar [this message]
2009-03-23 13:48                         ` Alexey Dobriyan
2009-03-23 15:14                           ` Oleg Nesterov
2009-03-23 21:44                             ` Theodore Tso
2009-03-30 22:18                               ` Andrew Morton
2009-03-30 22:52                                 ` Frank Ch. Eigler
2009-03-31  9:17                                 ` Peter Zijlstra
2009-03-31 11:27                                   ` Peter Zijlstra
2009-03-31 11:38                                   ` Frank Ch. Eigler
2009-03-31 16:25                                   ` Christoph Hellwig
2009-03-31 20:54                                     ` Roland McGrath
2009-03-21 21:48                 ` Frank Ch. Eigler
2009-03-22 12:08                   ` Ingo Molnar
2009-03-22 12:53                     ` Ingo Molnar
2009-03-23 20:25                     ` Frank Ch. Eigler
2009-03-23 20:39                       ` Linus Torvalds
2009-03-23  5:09               ` Roland McGrath
2009-03-24  5:29               ` Ananth N Mavinakayanahalli
2009-03-24  5:54                 ` Andrew Morton
2009-03-24  6:10                   ` Ananth N Mavinakayanahalli
2009-03-23  4:49         ` Roland McGrath
2009-03-23  6:34           ` Ingo Molnar

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=20090322123749.GF19826@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=fche@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=roland@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --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