linux-kernel - Re: [PATCH] Provide ways of crashing the kernel through debugfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1264689482.1973.132.camel@localhost>
Date:	Thu, 28 Jan 2010 16:38:02 +0200
From:	Artem Bityutskiy <dedekind1@...il.com>
To:	Américo Wang <xiyou.wangcong@...il.com>
Cc:	Simon Kagstrom <simon.kagstrom@...insight.net>,
	linux-kernel@...r.kernel.org,
	David Woodhouse <dwmw2@...radead.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] Provide ways of crashing the kernel through debugfs

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@...insight.net> wrote:
> > 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.
> >
> 
> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/