All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@kernel.org>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, ak@suse.de,
	akpm@linux-foundation.org, dipankar@in.ibm.com,
	randy.dunlap@oracle.com
Subject: Re: [PATCH] prohibit rcutorture from being compiled into the kernel
Date: Tue, 15 May 2007 23:42:31 -0700	[thread overview]
Message-ID: <464AA7D7.2040602@kernel.org> (raw)
In-Reply-To: <20070516002720.GA22379@linux.vnet.ibm.com>

Paul E. McKenney wrote:
> There have been a number of instances where people have accidentally
> compiled rcutorture into the kernel (CONFIG_RCU_TORTURE_TEST=y), which
> has never been useful, and has often resulted in great frustration.  The
> attached patch prohibits rcutorture from being compiled into the kernel.
> It may be excluded altogether or compiled as a module.  People wishing
> to have rcutorture hammer their machine immediately upon boot are free
> to hand-edit lib/Kconfig.debug to remove the "depends on m" line.
> 
> Thanks to Randy Dunlap for the trick that makes this work.
> 
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>

This seems reasonable to me.  I can imagine legitimate reasons to want to
have rcutorture running as early as possible, but as you said, anyone
wishing to do so can hand-edit lib/Kconfig.debug easily enough.

Acked-by: Josh Triplett <josh@kernel.org>

- Josh Triplett


      reply	other threads:[~2007-05-16  6:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16  0:27 [PATCH] prohibit rcutorture from being compiled into the kernel Paul E. McKenney
2007-05-16  6:42 ` Josh Triplett [this message]

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=464AA7D7.2040602@kernel.org \
    --to=josh@kernel.org \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=randy.dunlap@oracle.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.