Re: [BUILD BUG][3.16-rc3] Error: too many copied sections (max = 13)

[Konrad Rzeszutek Wilk]

On Wed, Jul 02, 2014 at 02:28:36PM -0700, Andrew Morton wrote:
> On Tue, 1 Jul 2014 00:09:13 -0400 Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:
> 
> > Testing the latest kernel (3.16-rc3) I hit this build bug:
> > 
> >   VDSO2C  arch/x86/vdso/vdso-image-64.c
> > Error: too many copied sections (max = 13)
> > /arch/x86/vdso/Makefile:61: recipe for target 'arch/x86/vdso/vdso-image-64.c' failed
> > make[3]: *** [arch/x86/vdso/vdso-image-64.c] Error 1
> > /scripts/Makefile.build:404: recipe for target 'arch/x86/vdso' failed
> > make[2]: *** [arch/x86/vdso] Error 2
> > 
> > I bisected it down to this commit:
> > 
> > commit 0e3727a8839c988a3c56170bc8da76d55a16acad
> > Author: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
> > Date:   Wed Jun 18 15:59:49 2014 -0700
> > 
> >     x86/vdso: Remove some redundant in-memory section headers
> > 
> > When I revert this commit, it compiles fine.
> 
> When I revert that I get
> 
> Error: cannot handle memsz != filesz
> make[2]: *** [arch/x86/vdso/vdso-image-64.c] Error 1
> make[1]: *** [arch/x86/vdso] Error 2
> make[1]: *** Waiting for unfinished jobs....
> In file included from include/linux/poll.h:11,
>                  from include/linux/ring_buffer.h:7,
>                  from include/linux/ftrace_event.h:5,
>                  from include/trace/syscall.h:6,
>                  from include/linux/syscalls.h:80,
>                  from kernel/capability.c:17:
> 
> Productivity decline...

When I revert that mentioned commit I get
Error: too many copied sections (max = 16)

But if I revert bfad381c0d1e19cae8461e105d8d4387dd2a14fe as well
then everything is back to normal.

> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/