All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	David Woodhouse <dwmw2@infradead.org>,
	Artem Bityutskiy <dedekind1@gmail.com>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] Provide ways of crashing the kernel through debugfs
Date: Wed, 27 Jan 2010 08:09:50 +0100	[thread overview]
Message-ID: <20100127080950.15685695@marrow.netinsight.se> (raw)
In-Reply-To: <2375c9f91001261853t1158a66aw86546a61e613338f@mail.gmail.com>

On Wed, 27 Jan 2010 10:53:23 +0800
Américo Wang <xiyou.wangcong@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

  reply	other threads:[~2010-01-27  7:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26  9:56 [PATCH] Provide ways of crashing the kernel through debugfs Simon Kagstrom
2010-01-26 10:08 ` Américo Wang
2010-01-26 10:18   ` Simon Kagstrom
2010-01-27  2:53     ` Américo Wang
2010-01-27  7:09       ` Simon Kagstrom [this message]
2010-01-28 14:38       ` Artem Bityutskiy
2010-01-29  6:13         ` Simon Kagstrom
2010-01-29 10:33           ` Andrew Morton
2010-02-02  4:16             ` Eric W. Biederman
2010-02-02  8:16               ` Simon Kagstrom
2010-02-03  8:52               ` [PATCH] lkdtm: Add debugfs access and loosen KPROBE ties Simon Kagstrom
2010-02-03 22:55                 ` Andrew Morton
2010-02-04  9:06                   ` [PATCH v2] " Simon Kagstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100127080950.15685695@marrow.netinsight.se \
    --to=simon.kagstrom@netinsight.net \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=xiyou.wangcong@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.