public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Sven Ladegast <sven@linux4geeks.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: KLive: Linux Kernel Live Usage Monitor
Date: Tue, 30 Aug 2005 16:56:02 +0200	[thread overview]
Message-ID: <20050830145602.GN8515@g5.random> (raw)
In-Reply-To: <Pine.LNX.4.63.0508300954190.1984@cassini.linux4geeks.de>

On Tue, Aug 30, 2005 at 10:01:21AM +0200, Sven Ladegast wrote:
> [..] combined 
> with an automatic oops/panic/bug-report this would be _very_ useful I think.

That would be nice addition IMHO. It'll be more complex since it'll
involve netconsole dumping and passing the klive session to the kernel
somehow (userland would be too unreliable to push the oops to the
server). The worst part is that oops dumping might expose random kernel
data (it could contain ssh keys as well), so I would either need to
purify the stack/code/register lines making the oops quite useless, or
not to show it at all (and only to show the count of the oopses
publically). A parameter could be used to tell the kernel if the whole
oops should be sent to the klive server or if only the notification an
oops should be sent (without sending the payload with potentially
sensitive data inside).

  parent reply	other threads:[~2005-08-30 14:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30  3:09 KLive: Linux Kernel Live Usage Monitor Andrea Arcangeli
2005-08-30  8:01 ` Sven Ladegast
2005-08-30  8:29   ` Rogier Wolff
2005-08-30  8:53     ` Sven Ladegast
2005-08-30  9:40       ` Rogier Wolff
2005-08-30  9:54         ` Bernd Petrovitsch
2005-08-30 15:10         ` Andrea Arcangeli
2005-08-30 16:33           ` Alan Cox
2005-08-30 16:16             ` Andrea Arcangeli
2005-08-30 16:56               ` Alan Cox
2005-08-30 16:40                 ` Andrea Arcangeli
2005-08-31 18:32               ` Pavel Machek
2005-09-01 15:19                 ` Andrea Arcangeli
2005-08-30 16:36             ` Jesper Juhl
2005-08-30 22:11         ` Bill Davidsen
2005-08-31  1:49           ` Andrea Arcangeli
2005-08-31 19:14             ` tony.luck
2005-08-31 19:47               ` Andrea Arcangeli
2005-09-05 18:26                 ` Andrea Arcangeli
2005-08-30 14:45     ` Andrea Arcangeli
2005-08-30 14:36   ` Alan Cox
2005-08-30 22:43     ` Sven Ladegast
2005-08-30 23:25       ` Alan Cox
2005-08-30 23:19         ` Sven Ladegast
2005-08-31 13:34           ` Alan Cox
2005-08-31 14:28             ` Sven Ladegast
2005-08-31 21:23               ` Andrea Arcangeli
2005-08-30 14:56   ` Andrea Arcangeli [this message]
2005-08-31 18:20     ` Pavel Machek
2005-09-01 15:23       ` Andrea Arcangeli
2005-09-01 12:26     ` Sven Ladegast
2005-09-05 22:05 ` Marc Giger
2005-09-05 23:13   ` Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2005-08-30 17:08 Wilkerson, Bryan P
2005-08-30 17:44 ` linux-os (Dick Johnson)
2005-08-30 20:31 ` Andrea Arcangeli

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=20050830145602.GN8515@g5.random \
    --to=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sven@linux4geeks.de \
    /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