Messages in this thread | | | Date | Tue, 26 Jan 2010 18:08:28 +0800 | Subject | Re: [PATCH] Provide ways of crashing the kernel through debugfs | From | Américo Wang <> |
| |
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.
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/
| |