Provide ways of crashing the kernel through debugfs
in [Kernel]
|
Prev: drivers/net/ariadne.c:165: error: 'set_multicast_list' undeclared here (not in a function)
Next: tty: usb_serial_mos7720: Fix get_lsr_info
From: Américo Wang on 26 Jan 2010 05:10 On Tue, Jan 26, 2010 at 5:56 PM, Simon Kagstrom <simon.kagstrom(a)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(a)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(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Simon Kagstrom on 26 Jan 2010 05:20 Hi Americo! On Tue, 26 Jan 2010 18:08:28 +0800 Américo Wang <xiyou.wangcong(a)gmail.com> wrote: > On Tue, Jan 26, 2010 at 5:56 PM, Simon Kagstrom > <simon.kagstrom(a)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(a)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. // Simon -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Américo Wang on 26 Jan 2010 22:00 On Tue, Jan 26, 2010 at 6:18 PM, Simon Kagstrom <simon.kagstrom(a)netinsight.net> wrote: > Hi Americo! > > On Tue, 26 Jan 2010 18:08:28 +0800 > Américo Wang <xiyou.wangcong(a)gmail.com> wrote: > >> On Tue, Jan 26, 2010 at 5:56 PM, Simon Kagstrom >> <simon.kagstrom(a)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(a)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(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Simon Kagstrom on 27 Jan 2010 02:20 On Wed, 27 Jan 2010 10:53:23 +0800 Américo Wang <xiyou.wangcong(a)gmail.com> wrote: > >> 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. I understand what you mean, and I'm fine if this doesn't get merged. Thanks for the comments! // Simon -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Artem Bityutskiy on 28 Jan 2010 09:40
On Wed, 2010-01-27 at 10:53 +0800, Américo Wang wrote: > On Tue, Jan 26, 2010 at 6:18 PM, Simon Kagstrom > <simon.kagstrom(a)netinsight.net> wrote: > > Hi Americo! > > > > On Tue, 26 Jan 2010 18:08:28 +0800 > > Américo Wang <xiyou.wangcong(a)gmail.com> wrote: > > > >> On Tue, Jan 26, 2010 at 5:56 PM, Simon Kagstrom > >> <simon.kagstrom(a)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(a)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. But Simon did explain in his first e-mail why he cares. You or others might care for similar reasons. -- Best Regards, Artem Bityutskiy (Артём Битюцкий) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |