From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752590Ab0A0CxZ (ORCPT ); Tue, 26 Jan 2010 21:53:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752060Ab0A0CxZ (ORCPT ); Tue, 26 Jan 2010 21:53:25 -0500 Received: from qw-out-2122.google.com ([74.125.92.25]:49739 "EHLO qw-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750900Ab0A0CxY convert rfc822-to-8bit (ORCPT ); Tue, 26 Jan 2010 21:53:24 -0500 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?= To: Simon Kagstrom Cc: linux-kernel@vger.kernel.org, David Woodhouse , Artem Bityutskiy , Ingo Molnar Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 26, 2010 at 6:18 PM, Simon Kagstrom wrote: > Hi Americo! > > On Tue, 26 Jan 2010 18:08:28 +0800 > Américo Wang wrote: > >> On Tue, Jan 26, 2010 at 5:56 PM, Simon Kagstrom >> 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 >> > --- >> > 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.