From: Peter Maydell <peter.maydell@linaro.org>
To: Pavel Borzenkov <pavel.borzenkov@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fw_cfg: check return value of fread()
Date: Tue, 18 Oct 2011 18:30:54 +0100 [thread overview]
Message-ID: <CAFEAcA_SBfk9Rhthr6_sX-d3H1bkbUexmynucZZSmCVPVJgwpw@mail.gmail.com> (raw)
In-Reply-To: <1318958208-13965-1-git-send-email-pavel.borzenkov@gmail.com>
On 18 October 2011 18:16, Pavel Borzenkov <pavel.borzenkov@gmail.com> wrote:
> Spotted by Clang Analyzer
>
> Signed-off-by: Pavel Borzenkov <pavel.borzenkov@gmail.com>
> ---
> hw/fw_cfg.c | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/hw/fw_cfg.c b/hw/fw_cfg.c
> index 8df265c..1125e7d 100644
> --- a/hw/fw_cfg.c
> +++ b/hw/fw_cfg.c
> @@ -113,6 +113,13 @@ static FILE *probe_splashfile(char *filename, int *file_sizep, int *file_typep)
> if (file_type == BMP_FILE) {
> fseek(fp, 28, SEEK_SET);
> fop_ret = fread(buf, 1, 2, fp);
> + if (fop_ret != 2) {
> + error_report("Could not read bpp value from '%s': %s",
> + filename, strerror(errno));
> + fclose(fp);
> + fp = NULL;
> + return fp;
> + }
> bmp_bpp = (buf[0] + (buf[1] << 8)) & 0xffff;
> if (bmp_bpp != 24) {
> error_report("only 24bpp bmp file is supported.");
Yuck, this code again. We should just replace it with
g_file_get_contents() and looking at the resulting buffer.
That would be 10% of the code and much less bug-ridden.
FWIW, strictly speaking there isn't a need to check the result
of the fread() because if we don't read the data then buf[] will
still have the BMP_FILE signature in it and the != 24 check will
fail.
Not checking the return code from that fseek(), on the other hand...
-- PMM
prev parent reply other threads:[~2011-10-18 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 17:16 [Qemu-devel] [PATCH] fw_cfg: check return value of fread() Pavel Borzenkov
2011-10-18 17:30 ` Peter Maydell [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=CAFEAcA_SBfk9Rhthr6_sX-d3H1bkbUexmynucZZSmCVPVJgwpw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=pavel.borzenkov@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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).