Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Mark Wielaard <mark@klomp.org>,
	Jesper Dangaard Brouer <brouer@redhat.com>,
	Jiri Olsa <jolsa@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
Subject: Re: Kernel build error on BTFIDS vmlinux
Date: Wed, 19 Aug 2020 16:34:30 +0100	[thread overview]
Message-ID: <0ddf7bc5-be05-cc06-05d7-2778c53d023b@redhat.com> (raw)
In-Reply-To: <c9c4a42ba6b4d36e557a5441e90f7f4961ec3f72.camel@klomp.org>

Hi Mark,

> Adding Nick, the binutils maintainer, so we can make sure
> binutils/elfutils agree on some ELF section compression corner case.

Thanks for doing this.

> But it would obviously be better if that wasn't necessary. So I'll try
> to fix libelf so that if it fixes up the alignment when reading the
> compressed data, it also does that when writing out the data again. But
> that would only help for a new version of elfutils.
> 
> So it would be nice if binutils ld could also be fixed to write out
> compressed sections with the correct alignment.

OK, I will look into doing this.

By any chance is there a small test case that you are using to check
this behaviour ?   If so, please may I have a copy for myself ?

Cheers
  Nick




  reply	other threads:[~2020-08-19 15:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18  8:55 Jesper Dangaard Brouer
2020-08-18  9:14 ` Jiri Olsa
2020-08-18 10:56   ` Jiri Olsa
2020-08-18 13:45     ` Jiri Olsa
2020-08-18 16:33       ` Jesper Dangaard Brouer
2020-08-18 17:29         ` Mark Wielaard
2020-08-19 15:34           ` Nick Clifton [this message]
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=0ddf7bc5-be05-cc06-05d7-2778c53d023b@redhat.com \
    --to=nickc@redhat.com \
    --cc=andriin@fb.com \
    --cc=brouer@redhat.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@klomp.org \
    --cc=netdev@vger.kernel.org \
    --cc=sdf@google.com \
    --subject='Re: Kernel build error on BTFIDS vmlinux' \
    /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

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).