[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100126111853.10890fc6@marrow.netinsight.se>
Date: Tue, 26 Jan 2010 11:18:53 +0100
From: Simon Kagstrom <simon.kagstrom@...insight.net>
To: Américo Wang <xiyou.wangcong@...il.com>
Cc: linux-kernel@...r.kernel.org,
David Woodhouse <dwmw2@...radead.org>,
Artem Bityutskiy <dedekind1@...il.com>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] Provide ways of crashing the kernel through debugfs
Hi Americo!
On Tue, 26 Jan 2010 18:08:28 +0800
Américo Wang <xiyou.wangcong@...il.com> wrote:
> On Tue, Jan 26, 2010 at 5:56 PM, Simon Kagstrom
> <simon.kagstrom@...insight.net> wrote:
> > For development and testing it's sometimes useful to crash or injure the
> > kernel in various ways. This patch adds a debugfs interface to provoke
> > null-pointer dereferences, stack corruption, panics, bugons etc. For
> > example:
> >
> > mount -t debugfs debugfs /mnt
> > echo 1 > /mnt/provoke-crash/null_dereference
> >
> > Signed-off-by: Simon Kagstrom <simon.kagstrom@...insight.net>
> > ---
> > Obviously this feature is for debugging and testing only, and of
> > interest to fairly few people. I've used it for testing the kmsg_dump
> > stuff (hence the CC:s above) and kdump, and have found it fairly useful.
> >
> > If it's not of interest, at least this mail will be in the archives if
> > someone else needs something like it :-)
>
> Hey, we already have /proc/sysrq-trigger, you need to state why
> it is better than using /proc/sysrq-trigger.
Well, it provides a few more ways of crashing the kernel. That's
basically the only additional feature you'll get.
// Simon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists