All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: ankita@in.ibm.com
Cc: linux-kernel@vger.kernel.org, fernando@oss.ntt.co.jp, maneesh@in.ibm.com
Subject: Re: [RFC] Linux Kernel Dump Test Module
Date: Thu, 7 Sep 2006 13:48:50 -0700	[thread overview]
Message-ID: <20060907134850.c05f3be2.akpm@osdl.org> (raw)
In-Reply-To: <20060907135329.GA17937@in.ibm.com>

On Thu, 7 Sep 2006 19:23:29 +0530
Ankita Garg <ankita@in.ibm.com> wrote:

> Please find below a patch for a simple module to test Linux Kernel Dump 
> mechanism. This module uses jprobes to install/activate pre-defined crash
> points. At different crash points, various types of crashing scenarios 
> are created like a BUG(), panic(), exception, recursive loop and stack 
> overflow. The user can activate a crash point with specific type by
> providing parameters at the time of module insertion. Please see the file
> header for usage information. The module is based on the Linux Kernel
> Dump Test Tool by Fernando <http://lkdtt.sourceforge.net>.
> 
> This module could be merged with mainline. Jprobes is used here so that the 
> context in which crash point is hit, could be maintained. This implements
> all the crash points as done by LKDTT except the one in the middle of 
> tasklet_action(). 

"could be merged with mainline": why "could"?  What would be the
disadvantages of doing this?

I think having test code like this in mainline is a good idea, particularly
for a subsystem like [kj]probes.

It's a bit regrettable that the code "knows" about particular not-exported,
arch-specific core kernel functions, but I guess those don't change very
often, so we won't be forever patching this module.



  reply	other threads:[~2006-09-07 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 13:53 [RFC] Linux Kernel Dump Test Module Ankita Garg
2006-09-07 20:48 ` Andrew Morton [this message]
2006-09-07 21:05   ` Maneesh Soni
2006-09-10 13:36 ` fernando
     [not found] ` <20060908004244.6ef7deb7.akpm@osdl.org>
2006-09-12  3:00   ` Ankita Garg

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=20060907134850.c05f3be2.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ankita@in.ibm.com \
    --cc=fernando@oss.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maneesh@in.ibm.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.