From: Al Viro <viro@ZenIV.linux.org.uk>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: [PATCH] Re: alpha: undefined reference to `save_stack_trace'
Date: Fri, 31 Oct 2008 18:55:26 +0000 [thread overview]
Message-ID: <20081031185526.GT28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20081031184822.GS28946@ZenIV.linux.org.uk>
On Fri, Oct 31, 2008 at 06:48:22PM +0000, Al Viro wrote:
> On Fri, Oct 31, 2008 at 06:24:11PM +0000, Al Viro wrote:
> > On Fri, Oct 31, 2008 at 07:57:51PM +0300, Alexey Dobriyan wrote:
> > > On alpha-smp-[ny]-debug-y:
> > >
> > > LD .tmp_vmlinux1
> > > kernel/built-in.o: In function `ftrace_trace_stack':
> > > (.text+0x706fc): undefined reference to `save_stack_trace'
> > >
> > >
> > > Somehow STACKTRACE is set despite no STACKTRACE_SUPPORT.
> >
> > select blows, film at 11. TRACING blindly selects STACKTRACE, with a bunch
> > of stuff in kernel/tracing/Kconfig doing select of TRACING. Not just an alpha
> > problem, BTW.
>
> While we are at it, we have that particular turd on allmodconfigs on (at least)
> alpha
> blackfin
> cris
> frv
> h8300
> ia64
> m32r
> m68k
> m68knommu
> mn10300
> parisc
> sparc (32bit one, that is)
> uml/i386
> uml/amd64
> xtensa
>
> We could slap && HAS_STACKTRACE_SUPPORT on all symbols that end up selecting
> TRACING, but that's almost certainly wrong; the thing won't break if we
> simply omit stack trace output on configs that do not have them supported.
> Why do we have that select STACKTRACE there, anyway?
It's too ugly for words, but it does deal with this mess ;-/
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
---
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index b58f43b..33dbefd 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -25,7 +25,7 @@ config TRACING
bool
select DEBUG_FS
select RING_BUFFER
- select STACKTRACE
+ select STACKTRACE if STACKTRACE_SUPPORT
select TRACEPOINTS
select NOP_TRACER
next prev parent reply other threads:[~2008-10-31 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 16:57 alpha: undefined reference to `save_stack_trace' Alexey Dobriyan
2008-10-31 18:24 ` Al Viro
2008-10-31 18:48 ` Al Viro
2008-10-31 18:55 ` Al Viro [this message]
2008-10-31 19:06 ` [PATCH] " Al Viro
2008-10-31 19:50 ` Al Viro
2008-10-31 20:05 ` Steven Rostedt
2008-10-31 20:13 ` Al Viro
2008-11-03 9:11 ` Ingo Molnar
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=20081031185526.GT28946@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.