From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>, luto@amacapital.net
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@amacapital.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
boris.ostrovsky@oracle.com
Subject: Re: [BUILD BUG][3.16-rc3] Error: too many copied sections (max = 13)
Date: Thu, 3 Jul 2014 13:52:22 -0400 [thread overview]
Message-ID: <20140703175222.GA13710@konrad-lan.dumpdata.com> (raw)
In-Reply-To: <20140702142836.084d1ad63b049d53a2f51218@linux-foundation.org>
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@goodmis.org> 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@amacapital.net>
> > 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2014-07-03 17:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 4:09 [BUILD BUG][3.16-rc3] Error: too many copied sections (max = 13) Steven Rostedt
2014-07-01 5:09 ` Andy Lutomirski
2014-07-01 14:49 ` Steven Rostedt
2014-07-01 14:58 ` Andy Lutomirski
2014-07-01 20:43 ` Steven Rostedt
2014-07-02 13:21 ` Steven Rostedt
2014-07-02 20:00 ` Andy Lutomirski
2014-07-02 20:05 ` H. Peter Anvin
2014-07-02 20:07 ` Andy Lutomirski
2014-07-02 20:18 ` H. Peter Anvin
2014-07-02 21:28 ` Andrew Morton
2014-07-02 21:30 ` Andy Lutomirski
2014-07-03 17:52 ` Konrad Rzeszutek Wilk [this message]
2014-07-03 18:07 ` Boris Ostrovsky
2014-07-03 18:06 ` Andy Lutomirski
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=20140703175222.GA13710@konrad-lan.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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 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.