From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Dan Aloni <da-x@monatomic.org>,
Bernhard Walle <bwalle@suse.de>,
Roland McGrath <roland@redhat.com>
Subject: Re: [PATCH] Add ELF note with Linux version
Date: Fri, 14 Sep 2007 12:47:00 -0700 [thread overview]
Message-ID: <46EAE534.5030900@goop.org> (raw)
In-Reply-To: <20070914060805.GA32169@uranus.ravnborg.org>
Sam Ravnborg wrote:
> On Thu, Sep 13, 2007 at 03:44:13PM -0700, Jeremy Fitzhardinge wrote:
>
>> It was originally there to put ELF notes into the vdso objects. I'm
>> using it to create notes in vmlinux for Xen, and apparently people are
>> using it to put other metadata into their kernel images.
>>
> From a post on arm-kernel:
>
>
>> With build-id binutils (e.g. the latest bintuils 2.18), objcopy produces
>> a 3.1 Gbytes Image file.
>>
>
> This seems outright silly.
> Either we should revert the notes changes or someone caring about it
> should sweep all archs and make sure it does not hurt there.
Hm, sounds like yet another binutils bug; unfortunately common when ELF
notes are about. Was there any further effort to isolate what was
causing the problem?
J
next prev parent reply other threads:[~2007-09-14 19:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 15:00 [PATCH] Add ELF note with Linux version Bernhard Walle
2007-09-06 10:36 ` Jeremy Fitzhardinge
2007-09-13 21:42 ` Andrew Morton
2007-09-13 21:56 ` Jeremy Fitzhardinge
2007-09-14 7:52 ` Bernhard Walle
2007-09-14 20:00 ` Jeremy Fitzhardinge
2007-09-13 22:13 ` Sam Ravnborg
2007-09-13 22:44 ` Jeremy Fitzhardinge
2007-09-14 6:08 ` Sam Ravnborg
2007-09-14 19:47 ` Jeremy Fitzhardinge [this message]
2007-09-14 21:07 ` Sam Ravnborg
2007-09-14 21:15 ` Roland McGrath
2007-09-14 21:31 ` Jeremy Fitzhardinge
2007-09-15 1:30 ` Roland McGrath
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=46EAE534.5030900@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=bwalle@suse.de \
--cc=da-x@monatomic.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox