DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=Ql0OwYZ9vrT8YHXYYgy8/shoMWFOXKGbGiUFP2ZIg2rl0cPx9p9/XDc4JO1Ib2zlir
         0yNLpHoWdeG62KxPjWh8A9m4ZFLScWb3Y7xUpCQCVj51/K3sRSpNzbTucnRdA4fJPFdC
         o9sLFnPH0+WclRv8mon8bDJu4Iw7vNBoUeW4o=
MIME-Version: 1.0
In-Reply-To: <20100126111853.10890fc6@marrow.netinsight.se>
References: <20100126105640.6bf9488c@marrow.netinsight.se>
	 <2375c9f91001260208t31379702tb49cb57d12d5890b@mail.gmail.com>
	 <20100126111853.10890fc6@marrow.netinsight.se>
Date: Wed, 27 Jan 2010 10:53:23 +0800
Message-ID: <2375c9f91001261853t1158a66aw86546a61e613338f@mail.gmail.com>
Subject: Re: [PATCH] Provide ways of crashing the kernel through debugfs
From: =?UTF-8?Q?Am=C3=A9rico_Wang?= <xiyou.wangcong@gmail.com>
To: Simon Kagstrom <simon.kagstrom@netinsight.net>
Cc: linux-kernel@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>,
       Artem Bityutskiy <dedekind1@gmail.com>, Ingo Molnar <mingo@elte.hu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1655
Lines: 42

On Tue, Jan 26, 2010 at 6:18 PM, Simon Kagstrom
<simon.kagstrom@netinsight.net> wrote:
> Hi Americo!
>
> On Tue, 26 Jan 2010 18:08:28 +0800
> Américo Wang <xiyou.wangcong@gmail.com> wrote:
>
>> On Tue, Jan 26, 2010 at 5:56 PM, Simon Kagstrom
>> <simon.kagstrom@netinsight.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@netinsight.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.
>

Yeah, I can see that, but why do I need to care how I crash the kernel
as long as I can crash it in a way.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/