From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: Giuseppe Musacchio <thatlemon@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>,
Riku Voipio <riku.voipio@iki.fi>,
Laurent Vivier <laurent@vivier.eu>
Subject: [Qemu-devel] [PULL v2 5/7] linux-user: elf: Map empty PT_LOAD segments
Date: Fri, 10 May 2019 12:45:34 +0200 [thread overview]
Message-ID: <20190510104536.17483-6-laurent@vivier.eu> (raw)
In-Reply-To: <20190510104536.17483-1-laurent@vivier.eu>
From: Giuseppe Musacchio <thatlemon@gmail.com>
Some PT_LOAD segments may be completely zeroed out and their p_filesize
is zero, in that case the loader should just allocate a page that's at
least p_memsz bytes large (plus eventual alignment padding).
Calling zero_bss does this job for us, all we have to do is make sure we
don't try to mmap a zero-length page.
Signed-off-by: Giuseppe Musacchio <thatlemon@gmail.com>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Message-Id: <20190503122007.lkjsvztgt4ycovac@debian>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
---
linux-user/elfload.c | 18 +++++++++++++-----
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/linux-user/elfload.c b/linux-user/elfload.c
index d08fe2346683..ef42e02d8233 100644
--- a/linux-user/elfload.c
+++ b/linux-user/elfload.c
@@ -2366,11 +2366,19 @@ static void load_elf_image(const char *image_name, int image_fd,
vaddr_ps = TARGET_ELF_PAGESTART(vaddr);
vaddr_len = TARGET_ELF_PAGELENGTH(eppnt->p_filesz + vaddr_po);
- error = target_mmap(vaddr_ps, vaddr_len,
- elf_prot, MAP_PRIVATE | MAP_FIXED,
- image_fd, eppnt->p_offset - vaddr_po);
- if (error == -1) {
- goto exit_perror;
+ /*
+ * Some segments may be completely empty without any backing file
+ * segment, in that case just let zero_bss allocate an empty buffer
+ * for it.
+ */
+ if (eppnt->p_filesz != 0) {
+ error = target_mmap(vaddr_ps, vaddr_len, elf_prot,
+ MAP_PRIVATE | MAP_FIXED,
+ image_fd, eppnt->p_offset - vaddr_po);
+
+ if (error == -1) {
+ goto exit_perror;
+ }
}
vaddr_ef = vaddr + eppnt->p_filesz;
--
2.20.1
next prev parent reply other threads:[~2019-05-10 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 10:45 [Qemu-devel] [PULL v2 0/7] Linux user for 4.1 patches Laurent Vivier
2019-05-10 10:45 ` [Qemu-devel] [PULL v2 1/7] linux-user: Add missing IPV6 sockopts Laurent Vivier
2019-05-10 10:45 ` [Qemu-devel] [PULL v2 2/7] linux-user/elfload: Fix GCC 9 build warnings Laurent Vivier
2019-05-10 10:45 ` [Qemu-devel] [PULL v2 3/7] linux-user: avoid string truncation warnings in uname field copying Laurent Vivier
2019-05-10 10:45 ` [Qemu-devel] [PULL v2 4/7] The ioctl(SIOCGIFNAME) call requires a struct ifreq Laurent Vivier
2019-05-10 10:45 ` Laurent Vivier [this message]
2019-05-10 10:45 ` [Qemu-devel] [PULL v2 6/7] linux-user: avoid treading on gprof's SIGPROF signals Laurent Vivier
2019-05-10 10:45 ` [Qemu-devel] [PULL v2 7/7] linux-user: fix GPROF build failure Laurent Vivier
2019-05-10 12:32 ` [Qemu-devel] [PULL v2 0/7] Linux user for 4.1 patches Peter Maydell
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=20190510104536.17483-6-laurent@vivier.eu \
--to=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=thatlemon@gmail.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 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).