From: Arjan van de Ven <arjan@linux.intel.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
systemtap@sources.redhat.com
Subject: Re: notification for systemtap-related oops
Date: Fri, 16 May 2008 12:47:29 -0700 [thread overview]
Message-ID: <482DE4D1.5020608@linux.intel.com> (raw)
In-Reply-To: <y0mskwif5hm.fsf@ton.toronto.redhat.com>
Frank Ch. Eigler wrote:
> Hi -
>
> Arjan, would it be possible for kerneloops.org to notify us systemtap
> people (cc:d) automagically if the oops messages implicate systemtap
> modules by including "stap_.*" in the loaded-module list or stack
> backtrace symbols?
I can get you an RSS feed for that....
doing something more proactive is harder due to the unscalable nature
next prev parent reply other threads:[~2008-05-16 19:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 16:41 Top kernel oopses/warnings for the week of May 16th 2008 Arjan van de Ven
2008-05-16 17:14 ` Evgeniy Polyakov
2008-05-16 18:04 ` Adrian Bunk
2008-05-16 18:19 ` Arjan van de Ven
2008-05-20 3:53 ` Dave Jones
2008-05-16 18:50 ` notification for systemtap-related oops Frank Ch. Eigler
2008-05-16 19:47 ` Arjan van de Ven [this message]
2008-05-16 20:23 ` Frank Ch. Eigler
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=482DE4D1.5020608@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=fche@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=systemtap@sources.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.