From: Borislav Petkov <bp@amd64.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Petkov, Borislav" <Borislav.Petkov@amd.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: build failure after merge of the moduleh tree
Date: Wed, 28 Sep 2011 09:58:45 +0200 [thread overview]
Message-ID: <20110928075845.GB30838@aftab> (raw)
In-Reply-To: <20110928174214.17a58be15d84d67c185930e1@canb.auug.org.au>
On Wed, Sep 28, 2011 at 03:42:14AM -0400, Stephen Rothwell wrote:
> Hi Paul,
>
> After merging the moduleh tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> arch/x86/kernel/sys_x86_64.c:28:10: warning: 'enum align_flags' declared inside parameter list
> arch/x86/kernel/sys_x86_64.c:28:10: warning: its scope is only this definition or declaration, which is probably not what you want
> arch/x86/kernel/sys_x86_64.c:28:22: error: parameter 3 ('flags') has incomplete type
> arch/x86/kernel/sys_x86_64.c:27:15: warning: function declaration isn't a prototype
> arch/x86/kernel/sys_x86_64.c: In function 'align_addr':
> arch/x86/kernel/sys_x86_64.c:33:6: error: 'va_align' undeclared (first use in this function)
> arch/x86/kernel/sys_x86_64.c:33:6: note: each undeclared identifier is reported only once for each function it appears in
> arch/x86/kernel/sys_x86_64.c:33:2: error: implicit declaration of function 'mmap_is_ia32'
> arch/x86/kernel/sys_x86_64.c:39:17: error: 'ALIGN_VDSO' undeclared (first use in this function)
> arch/x86/kernel/sys_x86_64.c:48:16: error: 'ALIGN_TOPDOWN' undeclared (first use in this function)
> arch/x86/kernel/sys_x86_64.c: In function 'control_va_addr_alignment':
> arch/x86/kernel/sys_x86_64.c:59:6: error: 'va_align' undeclared (first use in this function)
> arch/x86/kernel/sys_x86_64.c:69:20: error: 'ALIGN_VA_32' undeclared (first use in this function)
> arch/x86/kernel/sys_x86_64.c:71:20: error: 'ALIGN_VA_64' undeclared (first use in this function)
> arch/x86/kernel/sys_x86_64.c: In function 'arch_get_unmapped_area_topdown':
> arch/x86/kernel/sys_x86_64.c:231:11: error: 'ALIGN_TOPDOWN' undeclared (first use in this function)
>
> Presumably caused by commit dfb09f9b7ab0 ("x86, amd: Avoid cache aliasing
> penalties on AMD family 15h") from the tip tree interacting with the
> module.h split up.
>
> I applied the following patch (which could be applied to the tip
> tree ...).
>
> From 6b1212311c0728a7e3054e1f187e7c3b9f464bd5 Mon Sep 17 00:00:00 2001
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Wed, 28 Sep 2011 17:28:50 +1000
> Subject: [PATCH] x86, amd: include linux/elf.h since we use stuff from
> asm/elf.h
>
> The lack of this inclusion causes build erros after the module.h split up:
>
> arch/x86/kernel/sys_x86_64.c:28:10: warning: 'enum align_flags' declared inside parameter list
> arch/x86/kernel/sys_x86_64.c:28:10: warning: its scope is only this definition or declaration, which is probably not what you want
> arch/x86/kernel/sys_x86_64.c:28:22: error: parameter 3 ('flags') has incomplete type
> arch/x86/kernel/sys_x86_64.c:27:15: warning: function declaration isn't a prototype
> arch/x86/kernel/sys_x86_64.c: In function 'align_addr':
> arch/x86/kernel/sys_x86_64.c:33:6: error: 'va_align' undeclared (first use in this function)
> arch/x86/kernel/sys_x86_64.c:33:6: note: each undeclared identifier is reported only once for each function it appears in
> arch/x86/kernel/sys_x86_64.c:33:2: error: implicit declaration of function 'mmap_is_ia32'
> arch/x86/kernel/sys_x86_64.c:39:17: error: 'ALIGN_VDSO' undeclared (first use in this function)
> arch/x86/kernel/sys_x86_64.c:48:16: error: 'ALIGN_TOPDOWN' undeclared (first use in this function)
> arch/x86/kernel/sys_x86_64.c: In function 'control_va_addr_alignment':
> arch/x86/kernel/sys_x86_64.c:59:6: error: 'va_align' undeclared (first use in this function)
> arch/x86/kernel/sys_x86_64.c:69:20: error: 'ALIGN_VA_32' undeclared (first use in this function)
> arch/x86/kernel/sys_x86_64.c:71:20: error: 'ALIGN_VA_64' undeclared (first use in this function)
> arch/x86/kernel/sys_x86_64.c: In function 'arch_get_unmapped_area_topdown':
> arch/x86/kernel/sys_x86_64.c:231:11: error: 'ALIGN_TOPDOWN' undeclared (first use in this function)
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> arch/x86/kernel/sys_x86_64.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/kernel/sys_x86_64.c b/arch/x86/kernel/sys_x86_64.c
> index fe7d2da..0514890 100644
> --- a/arch/x86/kernel/sys_x86_64.c
> +++ b/arch/x86/kernel/sys_x86_64.c
> @@ -14,6 +14,7 @@
> #include <linux/personality.h>
> #include <linux/random.h>
> #include <linux/uaccess.h>
> +#include <linux/elf.h>
>
> #include <asm/ia32.h>
> #include <asm/syscalls.h>
Yep, it looks good, thanks Stephen. Btw, this is the second time
something like that happens as a result from the module split tree,
here's the first one: http://marc.info/?l=linux-kernel&m=131296515915227
It's a good thing we have linux-next! :-)
Thanks.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
next prev parent reply other threads:[~2011-09-28 7:58 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 7:42 linux-next: build failure after merge of the moduleh tree Stephen Rothwell
2011-09-28 7:58 ` Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-23 4:51 Stephen Rothwell
2012-03-23 12:49 ` Paul Gortmaker
2012-03-23 13:03 ` Stephen Rothwell
2011-11-01 7:38 Stephen Rothwell
2011-10-12 6:29 Stephen Rothwell
2011-10-11 8:39 Stephen Rothwell
2011-10-11 8:25 Stephen Rothwell
2011-10-11 13:05 ` Mark Brown
2011-10-04 7:32 Stephen Rothwell
2011-10-04 7:21 Stephen Rothwell
2011-10-04 15:24 ` Jonathan Cameron
2011-10-04 7:11 Stephen Rothwell
2011-10-04 7:03 Stephen Rothwell
2011-10-04 7:35 ` Kalle Valo
2011-10-04 8:14 ` Stephen Rothwell
2011-10-04 15:09 ` Larry Finger
2011-09-30 4:50 Stephen Rothwell
2011-09-30 12:52 ` Linus Walleij
2011-09-30 13:19 ` Stephen Rothwell
2011-10-03 6:55 ` Linus Walleij
2011-09-30 18:56 ` Paul Gortmaker
2011-09-28 8:41 Stephen Rothwell
2011-09-28 13:42 ` Paul Gortmaker
2011-09-29 0:15 ` Paul Gortmaker
2011-09-29 1:15 ` Stephen Rothwell
2011-09-28 8:35 Stephen Rothwell
2011-09-28 16:42 ` Kalle Valo
2011-09-28 8:25 Stephen Rothwell
2011-09-28 8:18 Stephen Rothwell
2011-10-09 5:08 ` Paul Gortmaker
2011-10-09 18:01 ` Chris Ball
2011-09-28 8:00 Stephen Rothwell
2011-09-28 7:50 Stephen Rothwell
2011-09-28 7:10 Stephen Rothwell
2011-08-23 5:08 Stephen Rothwell
2011-08-23 9:59 ` Felipe Balbi
2011-09-02 18:32 ` Geert Uytterhoeven
2011-09-05 10:39 ` Felipe Balbi
2011-08-10 1:49 Stephen Rothwell
2011-08-03 4:16 Stephen Rothwell
2011-08-03 14:26 ` Greg KH
2011-08-03 4:10 Stephen Rothwell
2011-08-02 5:13 Stephen Rothwell
2011-08-02 10:15 ` Alasdair G Kergon
2011-08-01 3:58 Stephen Rothwell
2011-07-29 7:09 Stephen Rothwell
2011-07-31 6:59 ` Paul Gortmaker
2011-07-29 7:06 Stephen Rothwell
2011-07-31 7:44 ` Paul Gortmaker
2011-08-01 0:30 ` Stephen Rothwell
2011-07-29 6:48 Stephen Rothwell
2011-07-31 7:30 ` Paul Gortmaker
2011-07-29 6:24 Stephen Rothwell
2011-07-31 7:26 ` Paul Gortmaker
2011-07-29 6:19 Stephen Rothwell
2011-07-31 8:08 ` Paul Gortmaker
2011-07-29 5:41 Stephen Rothwell
2011-07-29 5:30 Stephen Rothwell
2011-07-29 5:25 Stephen Rothwell
2011-07-29 5:37 ` Stephen Rothwell
2011-07-31 6:31 ` Paul Gortmaker
2011-07-31 8:14 ` Paul Gortmaker
2011-07-29 5:10 Stephen Rothwell
2011-07-30 19:03 ` Dmitry Torokhov
2011-07-29 5:10 Stephen Rothwell
2011-07-31 4:45 ` Paul Gortmaker
2011-07-29 4:56 Stephen Rothwell
2011-07-31 5:44 ` Paul Gortmaker
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=20110928075845.GB30838@aftab \
--to=bp@amd64.org \
--cc=Borislav.Petkov@amd.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).