public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: linux-ia64@vger.kernel.org
Subject: Re: fault-injection framework on ia64
Date: Thu, 15 Feb 2007 19:43:51 +0000	[thread overview]
Message-ID: <200702152043.52259.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20070215041554.8e9c92aa.akpm@linux-foundation.org>

On Thursday 15 February 2007 14:17, Andrew Morton wrote:
> On Thu, 15 Feb 2007 21:44:34 +0900 "Akinobu Mita" <akinobu.mita@gmail.com> 
wrote:
> > 2007/2/15, Andrew Morton <akpm@linux-foundation.org>:
> > > lib/built-in.o(.text+0x2c192): In function `should_fail':
> > > : undefined reference to `save_stack_trace'
> > >
> > > We could disable the feature on ia64, but then they wouldn't be able to
> > > inject faults.
> >
> > I couldn't understand this build error happend.
> > (I might misunderstand something)
> > Because IA64 config always disable CONFIG_STACKTRACE, so
> > should_fail() doesn't use save_stack_trace() in fail_stacktrace().
>
> OK.  Maybe this patch broke things:

But if STACKTRACE depends on STACKTRACE_SUPPORT, which isn't defined on ia64, 
kconfig should disable FAULT_INJECTION altogether with my patch (as it did 
before it). I don't think that FAULT_INJECTION could be enabled before my 
patch, right?

_BUT_ probably STACKTRACE_SUPPORT should be defined, with default n and no 
prompt, on ia64, or Kconfig gets confused (it should output a warning, 
like 'undefined symbol STACKTRACE_SUPPORT'). We on UML used to get warning 
when INPUT was used but not defined. Hmmm....

I'm interested in this because I also sent the patch to -stable, and Akinobu's 
patch would be worse to merge there.

> From: "Paolo 'Blaisorblade' Giarrusso" <blaisorblade@yahoo.it>
>
> There is no prompt for STACKTRACE, so it is enabled only when 'select'ed.
> FAULT_INJECTION depends on it, while LOCKDEP selects it.  So
> FAULT_INJECTION becomes visible in Kconfig only when LOCKDEP is enabled.
>
> Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
> Cc: <stable@kernel.org>
> Cc: Akinobu Mita <akinobu.mita@gmail.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
>  lib/Kconfig.debug |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -puN
> lib/Kconfig.debug~kconfig-fault_injection-can-be-selected-only-if-lockdep-i
>s-enabled lib/Kconfig.debug ---
> a/lib/Kconfig.debug~kconfig-fault_injection-can-be-selected-only-if-lockdep
>-is-enabled +++ a/lib/Kconfig.debug
> @@ -400,7 +400,7 @@ config LKDTM
>  config FAULT_INJECTION
>  	bool "Fault-injection framework"
>  	depends on DEBUG_KERNEL
> -	depends on STACKTRACE
> +	select STACKTRACE
>  	select FRAME_POINTER
>  	help
>  	  Provide fault-injection framework.
> _

-- 
Inform me of my mistakes, so I can add them to my list!
Paolo Giarrusso, aka Blaisorblade
http://www.user-mode-linux.org/~blaisorblade

Chiacchiera con i tuoi amici in tempo reale! 
 http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com 

  parent reply	other threads:[~2007-02-15 19:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 12:15 fault-injection framework on ia64 Andrew Morton
2007-02-15 12:44 ` Akinobu Mita
2007-02-15 13:17 ` Andrew Morton
2007-02-15 13:25 ` Akinobu Mita
2007-02-15 19:43 ` Blaisorblade [this message]
2007-02-16 17:30 ` Akinobu Mita

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=200702152043.52259.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=linux-ia64@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox