From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: netdev <netdev@vger.kernel.org>,
linux-next@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: bpf_slow_path: sibling call to `skb_copy_bits' not allowed multiple TOCs (ppc)
Date: Thu, 29 Mar 2012 14:30:40 +1100 [thread overview]
Message-ID: <20120329143040.6568ff46a45e6bd10d428473@canb.auug.org.au> (raw)
In-Reply-To: <CAP=VYLqwbjNDQ-TTbs_6cH4X2MMzy=MAFy4=R116zGL8a6qUag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
Hi Paul,
On Wed, 28 Mar 2012 20:54:56 -0400 Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
>
> coverage. Even in the absence of the skb error, it still fails to link with:
>
> "powerpc-linux-ld: TOC section size exceeds 64k"
>
> i.e. it never links into anything a person could actually try and boot anyway.
>
> So, just knowing "yes that is bogus because you've got a giant kernel
> with multiple TOC" would be useful information here.
This last message has been known for a long time and would require us to
change the way we link the kernel to fix. I had a go at it a year or so
ago, but ran into binutils bugs :-(
The other message may be a result of the TOC section size problem, but I
am not sure.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-03-29 3:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 0:54 bpf_slow_path: sibling call to `skb_copy_bits' not allowed multiple TOCs (ppc) Paul Gortmaker
2012-03-29 3:30 ` Stephen Rothwell [this message]
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=20120329143040.6568ff46a45e6bd10d428473@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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