From: Peter Maydell <peter.maydell@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PULL 09/21] linux-user: Add gen-vdso tool
Date: Thu, 2 Nov 2023 12:49:07 +0000 [thread overview]
Message-ID: <CAFEAcA-byuebJTYoHbVH2tvBffNRtwM4JvEUR8_B9iMGFkb66Q@mail.gmail.com> (raw)
In-Reply-To: <20231030211727.165090-10-richard.henderson@linaro.org>
On Mon, 30 Oct 2023 at 21:19, Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> This tool will be used for post-processing the linked vdso image,
> turning it into something that is easy to include into elfload.c.
>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
Hi; Coverity complains about the lack of error-checking
here (CID 1523742):
> + /*
> + * Read the input file into a buffer.
> + * We expect the vdso to be small, on the order of one page,
> + * therefore we do not expect a partial read.
> + */
> + fseek(inf, 0, SEEK_END);
> + total_len = ftell(inf);
> + fseek(inf, 0, SEEK_SET);
> +
> + buf = malloc(total_len);
We don't check for errors from fseek() or ftell(). In particular
this means that if ftell() returned -1 we pass -1 to malloc(),
which isn't valid.
> + if (buf == NULL) {
> + goto perror_inf;
> + }
This could all be sidestepped by using glib, which would give
us the higher level g_file_get_contents(), rather than spending
20 lines doing it with POSIX APIs.
thanks
-- PMM
next prev parent reply other threads:[~2023-11-02 12:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 21:17 [PULL 00/21] linux-user patch queue Richard Henderson
2023-10-30 21:17 ` [PULL 01/21] linux-user: Fix guest signal remapping after adjusting SIGABRT Richard Henderson
2023-10-30 21:17 ` [PULL 02/21] linux-user: Introduce imgsrc_read, imgsrc_read_alloc Richard Henderson
2023-10-30 21:17 ` [PULL 03/21] linux-user: Tidy loader_exec Richard Henderson
2023-10-30 21:17 ` [PULL 04/21] linux-user: Do not clobber bprm_buf swapping ehdr Richard Henderson
2023-10-30 21:17 ` [PULL 05/21] linux-user: Use ImageSource in load_elf_image Richard Henderson
2023-10-30 21:17 ` [PULL 06/21] linux-user: Use ImageSource in load_symbols Richard Henderson
2023-10-30 21:17 ` [PULL 07/21] linux-user: Replace bprm->fd with bprm->src.fd Richard Henderson
2023-10-30 21:17 ` [PULL 08/21] linux-user: Load vdso image if available Richard Henderson
2023-10-30 21:17 ` [PULL 09/21] linux-user: Add gen-vdso tool Richard Henderson
2023-11-02 12:49 ` Peter Maydell [this message]
2023-10-30 21:17 ` [PULL 10/21] linux-user/i386: Add vdso Richard Henderson
2023-10-30 21:17 ` [PULL 11/21] linux-user/x86_64: " Richard Henderson
2023-10-30 21:17 ` [PULL 12/21] linux-user/aarch64: " Richard Henderson
2023-10-30 21:17 ` [PULL 13/21] linux-user/arm: " Richard Henderson
2023-10-30 21:17 ` [PULL 14/21] linux-user/hppa: " Richard Henderson
2023-10-30 21:17 ` [PULL 15/21] linux-user/riscv: " Richard Henderson
2024-01-11 21:49 ` Vineet Gupta
2024-01-12 21:35 ` Richard Henderson
2024-01-12 23:04 ` Palmer Dabbelt
2024-01-12 23:37 ` Vineet Gupta
2024-01-12 23:58 ` Vineet Gupta
2024-01-13 0:05 ` Richard Henderson
2024-01-13 0:22 ` Vineet Gupta
2024-01-14 23:52 ` Richard Henderson
2023-10-30 21:17 ` [PULL 16/21] linux-user/loongarch64: " Richard Henderson
2023-10-30 21:17 ` [PULL 17/21] linux-user/ppc: " Richard Henderson
2023-10-30 21:17 ` [PULL 18/21] linux-user/s390x: Rename __SIGNAL_FRAMESIZE to STACK_FRAME_OVERHEAD Richard Henderson
2023-10-30 21:17 ` [PULL 19/21] linux-user/s390x: Add vdso Richard Henderson
2023-10-30 21:17 ` [PULL 20/21] linux-user: Show vdso address in /proc/pid/maps Richard Henderson
2023-10-30 21:17 ` [PULL 21/21] build: Add update-linux-vdso makefile rule Richard Henderson
2023-10-31 7:51 ` [PULL 00/21] linux-user patch queue Stefan Hajnoczi
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=CAFEAcA-byuebJTYoHbVH2tvBffNRtwM4JvEUR8_B9iMGFkb66Q@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 NNTP newsgroup(s).