All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	sdf@google.com, andriin@fb.com, Mark Wielaard <mjw@redhat.com>
Subject: Re: Kernel build error on BTFIDS vmlinux
Date: Tue, 18 Aug 2020 15:45:43 +0200	[thread overview]
Message-ID: <20200818134543.GD177896@krava> (raw)
In-Reply-To: <20200818105602.GC177896@krava>

On Tue, Aug 18, 2020 at 12:56:08PM +0200, Jiri Olsa wrote:
> On Tue, Aug 18, 2020 at 11:14:10AM +0200, Jiri Olsa wrote:
> > On Tue, Aug 18, 2020 at 10:55:55AM +0200, Jesper Dangaard Brouer wrote:
> > > 
> > > On latest DaveM net-git tree (06a4ec1d9dc652), after linking (LD vmlinux) the
> > > "BTFIDS vmlinux" fails. Are anybody else experiencing this? Are there already a
> > > fix? (just returned from vacation so not fully up-to-date on ML yet)
> > > 
> > > The tool which is called and error message:
> > >   ./tools/bpf/resolve_btfids/resolve_btfids vmlinux
> > >   FAILED elf_update(WRITE): invalid section alignment
> > 
> > hi,
> > could you send your .config as well?
> 
> reproduced.. checking on fix

I discussed this with Mark (cc-ed) it seems to be a problem
with linker when dealing with compressed debug info data,
which is enabled in your .config

it works for me when I disable CONFIG_DEBUG_INFO_COMPRESSED option

Mark will fix this upstream, meanwhile he suggested workaround
we can do in resolve_btfids tool, that I'll try to send shortly

thanks,
jirka


  reply	other threads:[~2020-08-18 13:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18  8:55 Kernel build error on BTFIDS vmlinux Jesper Dangaard Brouer
2020-08-18  9:14 ` Jiri Olsa
2020-08-18 10:56   ` Jiri Olsa
2020-08-18 13:45     ` Jiri Olsa [this message]
2020-08-18 16:33       ` Jesper Dangaard Brouer
2020-08-18 17:29         ` Mark Wielaard
2020-08-19 15:34           ` Nick Clifton
2020-08-19 17:18             ` Jiri Olsa
2020-08-19 22:00               ` Mark Wielaard
2020-08-20 12:14                 ` Nick Clifton

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=20200818134543.GD177896@krava \
    --to=jolsa@redhat.com \
    --cc=andriin@fb.com \
    --cc=brouer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjw@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=sdf@google.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 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.