From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gregor Haas <gregorhaas1997@gmail.com>
Cc: qemu-devel@nongnu.org, yaoxt.fnst@fujitsu.com
Subject: Re: [PATCH v2] hw/core/loader: allow loading larger ROMs
Date: Fri, 28 Jun 2024 09:12:19 +0100 [thread overview]
Message-ID: <Zn5wUyy2qWpUAtZo@redhat.com> (raw)
In-Reply-To: <20240628005817.1672298-1-gregorhaas1997@gmail.com>
On Thu, Jun 27, 2024 at 05:58:17PM -0700, Gregor Haas wrote:
> The read() syscall is not guaranteed to return all data from a file. The
> default ROM loader implementation currently does not take this into account,
> instead failing if all bytes are not read at once. This change loads the ROM
> using load_image_size() instead, which correctly reads all data using
> multiple calls to read().
>
> Signed-off-by: Gregor Haas <gregorhaas1997@gmail.com>
> ---
> hw/core/loader.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/hw/core/loader.c b/hw/core/loader.c
> index 2f8105d7de..8216781a75 100644
> --- a/hw/core/loader.c
> +++ b/hw/core/loader.c
> @@ -1115,14 +1115,13 @@ ssize_t rom_add_file(const char *file, const char *fw_dir,
>
> rom->datasize = rom->romsize;
> rom->data = g_malloc0(rom->datasize);
> - lseek(fd, 0, SEEK_SET);
> - rc = read(fd, rom->data, rom->datasize);
> + close(fd);
> + rc = load_image_size(rom->path, rom->data, rom->datasize);
> if (rc != rom->datasize) {
> fprintf(stderr, "rom: file %-20s: read error: rc=%zd (expected %zd)\n",
> rom->name, rc, rom->datasize);
> goto err;
> }
> - close(fd);
This method can be simplified much more.
All of the original 'open', lseek, g_malloc0, read & close, can be
replaced by something approximately like this (untested):
g_autoptr(GError) gerr = NULL;
if (!g_file_get_contents(file, &rom->data, &rom->datasize, &gerr)) {
fprintf(stderr, "unable to load ROM '%s': %s", file, gerr->message);
goto err;
}
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2024-06-28 8:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 0:58 [PATCH v2] hw/core/loader: allow loading larger ROMs Gregor Haas
2024-06-28 8:12 ` Daniel P. Berrangé [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=Zn5wUyy2qWpUAtZo@redhat.com \
--to=berrange@redhat.com \
--cc=gregorhaas1997@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=yaoxt.fnst@fujitsu.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).