From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] elfutils: Fix debugedit failure in grub
Date: Fri, 13 Jun 2014 11:06:23 -0500 [thread overview]
Message-ID: <539B217F.4060603@windriver.com> (raw)
In-Reply-To: <1402646310.12440.471.camel@ted>
On 6/13/14, 2:58 AM, Richard Purdie wrote:
> We've seeing occasional debugedit failures in grub during do_package
> which in turn are coming from section alignment failures from libelf.
> The failures occur when gold is used to link grub instead of ld.bfd.
>
> "readelf -e uhci.module" shows:
>
> Section Headers:
> [Nr] Name Type Addr Off Size ES Flg Lk Inf Al
> [12] .note.GNU-stack PROGBITS 00000000 0010ce 000000 00 0 0 1
>
> in a good build and:
>
> Section Headers:
> [Nr] Name Type Addr Off Size ES Flg Lk Inf Al
> [24] .note.GNU-stack PROGBITS 00000000 009180 000000 00 0 0 0
>
> in a bad build. The problem is the "Al" (alignment) change from 1 to 0.
> If its 0, debugedit complains.
>
> As far as I can tell, the alignment of a zero length section is not
> an issue and the check in libelf should check the section size and only
> give alignment errors if there is some data to align.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
While I haven't tried the fix, I agree, this is my understanding of what should
be happening as well. A zero size section should not complain.
--Mark
> diff --git a/meta/recipes-devtools/elfutils/elfutils-0.158/fixheadercheck.patch b/meta/recipes-devtools/elfutils/elfutils-0.158/fixheadercheck.patch
> new file mode 100644
> index 0000000..8796e9a
> --- /dev/null
> +++ b/meta/recipes-devtools/elfutils/elfutils-0.158/fixheadercheck.patch
> @@ -0,0 +1,24 @@
> +For some binaries we can get a invalid section alignment, for example if
> +sh_align = 1 and sh_addralign is 0. In the case of a zero size section like
> +".note.GNU-stack", this is irrelavent as far as I can tell and we shouldn't
> +error in this case.
> +
> +RP 2014/6/11
> +
> +Upstream-Status: Pending
> +
> +Index: elfutils-0.158/libelf/elf32_updatenull.c
> +===================================================================
> +--- elfutils-0.158.orig/libelf/elf32_updatenull.c 2012-12-14 22:40:48.000000000 +0000
> ++++ elfutils-0.158/libelf/elf32_updatenull.c 2014-06-11 16:35:43.417386291 +0000
> +@@ -327,8 +327,8 @@
> + we test for the alignment of the section being large
> + enough for the largest alignment required by a data
> + block. */
> +- if (unlikely (! powerof2 (shdr->sh_addralign))
> +- || unlikely (shdr->sh_addralign < sh_align))
> ++ if (shdr->sh_size && (unlikely (! powerof2 (shdr->sh_addralign))
> ++ || unlikely (shdr->sh_addralign < sh_align)))
> + {
> + __libelf_seterrno (ELF_E_INVALID_ALIGN);
> + return -1;
> diff --git a/meta/recipes-devtools/elfutils/elfutils_0.158.bb b/meta/recipes-devtools/elfutils/elfutils_0.158.bb
> index e425364..ef3dd0b 100644
> --- a/meta/recipes-devtools/elfutils/elfutils_0.158.bb
> +++ b/meta/recipes-devtools/elfutils/elfutils_0.158.bb
> @@ -25,13 +25,11 @@ SRC_URI += "\
> file://core_filename.patch \
> file://CVE-2014-0172.patch \
> file://unwind_non_linux.patch \
> -"
> -
> -SRC_URI += " \
> - file://elf_additions.diff \
> - file://mempcpy.patch \
> - file://dso-link-change.patch \
> - file://m4-biarch.m4-tweak-AC_RUN_IFELSE-for-cross-compiling.patch \
> + file://elf_additions.diff \
> + file://mempcpy.patch \
> + file://dso-link-change.patch \
> + file://m4-biarch.m4-tweak-AC_RUN_IFELSE-for-cross-compiling.patch \
> + file://fixheadercheck.patch \
> "
>
> # Only apply when building uclibc based target recipe
>
>
prev parent reply other threads:[~2014-06-13 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 7:58 [PATCH] elfutils: Fix debugedit failure in grub Richard Purdie
2014-06-13 16:06 ` Mark Hatle [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=539B217F.4060603@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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