From: Philippe Troin <phil@fifi.org>
To: Alexander Sandler <ASandler@store-age.com>
Cc: "'sathish jayapalan'" <sathish_jayapalan@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: How to crash a system and take a dump?
Date: 04 Feb 2002 18:32:21 -0800 [thread overview]
Message-ID: <87zo2oacay.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <BDE817654148D51189AC00306E063AAE054623@exchange.store-age.com>
In-Reply-To: <BDE817654148D51189AC00306E063AAE054623@exchange.store-age.com>
Alexander Sandler <ASandler@store-age.com> writes:
> > Hi,
> > I have a doubt. I know that linux kernel doesn't crash
> > so easily. Is there any way to panic the system? Can I
> > go to the source area and insert/modify a variable in
> > kernel code so that the kernel references a null
> > pointer and crashes while running the kernel compiled
> > with this variable. My aim is to learn crash dump
> > analysis with 'Lcrash tool". Please help me out with
> > this.
>
> Go to interrupt handler (for instance in fs/buffer.c end_buffer_io_async() )
> and cause segmentation fault.
> System will try to kill process that caused segmentation fault and since
> it's in interrupt context will panic.
Simplier: insmod this module:
#include <linux/module.h>
int init_module()
{
panic("Forcing panic");
}
int cleanup_module()
{
}
Phil.
next prev parent reply other threads:[~2002-02-05 2:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 11:40 How to crash a system and take a dump? Alexander Sandler
2002-02-05 2:32 ` Philippe Troin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-05 18:50 Alexander Sandler
2002-02-04 11:26 sathish jayapalan
2002-02-04 12:31 ` Gianni Tedesco
2002-02-04 13:32 ` Suparna Bhattacharya
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=87zo2oacay.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=ASandler@store-age.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sathish_jayapalan@yahoo.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.