From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/25083] unstrip tries to write out an enormous amount of data
Date: Sat, 26 Oct 2019 00:21:00 -0000 [thread overview]
Message-ID: <bug-25083-10460-LosjbaSkx4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25083-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25083
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Mark Wielaard <mark at klomp dot org> ---
commit 9d3003f6b0baa94a53013fbefb4f6542bc532a6c (HEAD -> master)
Author: Mark Wielaard <mark@klomp.org>
Date: Sun Oct 20 17:26:29 2019 +0200
unstrip: Add sanity check for bogus sh_offset of allocated sections.
unstrip tries to preserve any allocated section offset in an
executable or shared library. If the offset is extremely large that
would cause the disk to fill up because we will write out a file with
lots of padding to put the section contents at that particular
offset. Add a sanity check that makes sure we just error out if there
is such a bogus offset by checking that no offset is larger than the
original ELF file size.
https://sourceware.org/bugzilla/show_bug.cgi?id=25083
Signed-off-by: Mark Wielaard <mark@klomp.org>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-10-26 0:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 15:00 [Bug libelf/25083] New: Unexpected hangs at elf32_updatefile.c:518 leftcopy.chx at gmail dot com
2019-10-19 19:27 ` [Bug libelf/25083] " mark at klomp dot org
2019-10-20 3:43 ` leftcopy.chx at gmail dot com
2019-10-20 10:18 ` mark at klomp dot org
2019-10-20 15:24 ` mark at klomp dot org
2019-10-21 20:58 ` [Bug tools/25083] unstrip tries to write out an enormous amount of data mark at klomp dot org
2019-10-26 0:21 ` mark at klomp dot org [this message]
2020-07-28 4:46 ` meave390 at gmail dot com
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=bug-25083-10460-LosjbaSkx4@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).