From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Janosch Frank" <frankja@linux.ibm.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>
Subject: Re: [PATCH v4 1/7] dump: Replace tswapN() -> cpu_to_dumpN()
Date: Fri, 24 Feb 2023 08:00:36 +0100 [thread overview]
Message-ID: <52fa1fab-845c-0a2d-bf4d-4ce1a752e3e7@redhat.com> (raw)
In-Reply-To: <20230223231755.81633-2-philmd@linaro.org>
On 24/02/2023 00.17, Philippe Mathieu-Daudé wrote:
> All uses of tswap in that file are wrong, and should be using
> cpu_to_dumpN, which correctly tests the endianness of the output.
>
> Suggested-by: Richard Henderson <richard.henderson@linaro.org>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> dump/dump.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/dump/dump.c b/dump/dump.c
> index 279b07f09b..7101169ecb 100644
> --- a/dump/dump.c
> +++ b/dump/dump.c
> @@ -907,13 +907,13 @@ static void get_note_sizes(DumpState *s, const void *note,
> if (dump_is_64bit(s)) {
> const Elf64_Nhdr *hdr = note;
> note_head_sz = sizeof(Elf64_Nhdr);
> - name_sz = tswap64(hdr->n_namesz);
> - desc_sz = tswap64(hdr->n_descsz);
> + name_sz = cpu_to_dump64(s, hdr->n_namesz);
> + desc_sz = cpu_to_dump64(s, hdr->n_descsz);
> } else {
> const Elf32_Nhdr *hdr = note;
> note_head_sz = sizeof(Elf32_Nhdr);
> - name_sz = tswap32(hdr->n_namesz);
> - desc_sz = tswap32(hdr->n_descsz);
> + name_sz = cpu_to_dump32(s, hdr->n_namesz);
> + desc_sz = cpu_to_dump32(s, hdr->n_descsz);
> }
Those tswaps looked suspiciuous indeed.
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2023-02-24 7:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 23:17 [PATCH v4 0/7] dump: Make most of it target agnostic (build once) Philippe Mathieu-Daudé
2023-02-23 23:17 ` [PATCH v4 1/7] dump: Replace tswapN() -> cpu_to_dumpN() Philippe Mathieu-Daudé
2023-02-23 23:29 ` Richard Henderson
2023-02-24 7:00 ` Thomas Huth [this message]
2023-02-23 23:17 ` [PATCH v4 2/7] dump: Replace TARGET_PAGE_SIZE -> qemu_target_page_size() Philippe Mathieu-Daudé
2023-02-23 23:30 ` Richard Henderson
2023-02-24 7:01 ` Thomas Huth
2023-02-23 23:17 ` [PATCH v4 3/7] dump: Correct headers included Philippe Mathieu-Daudé
2023-02-23 23:32 ` Richard Henderson
2023-02-24 7:02 ` Thomas Huth
2023-02-23 23:17 ` [PATCH v4 4/7] dump: Introduce win_dump_available() Philippe Mathieu-Daudé
2023-02-23 23:43 ` Richard Henderson
2023-02-24 7:08 ` Thomas Huth
2023-02-23 23:17 ` [PATCH v4 5/7] dump: Introduce create_win_dump() Philippe Mathieu-Daudé
2023-02-23 23:43 ` Richard Henderson
2023-02-24 7:08 ` Thomas Huth
2023-02-23 23:17 ` [PATCH v4 6/7] dump: Build once by adding stubs for non-x86 targets Philippe Mathieu-Daudé
2023-02-23 23:51 ` Richard Henderson
2023-02-24 6:53 ` Philippe Mathieu-Daudé
2023-02-23 23:17 ` [PATCH v4 7/7] dump: Rename x86-specific file as win_dump_x86.c Philippe Mathieu-Daudé
2023-02-23 23:22 ` Philippe Mathieu-Daudé
2023-02-23 23:52 ` Richard Henderson
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=52fa1fab-845c-0a2d-bf4d-4ce1a752e3e7@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=frankja@linux.ibm.com \
--cc=marcandre.lureau@redhat.com \
--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).