From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
berrange@redhat.com
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v2 1/2] util/hexdump: fix QEMU_HEXDUMP_LINE_WIDTH logic
Date: Fri, 31 Oct 2025 21:54:04 +0100 [thread overview]
Message-ID: <d0f6aa76-08c6-4630-927e-358c8f81f383@linaro.org> (raw)
In-Reply-To: <20251031190246.257153-2-vsementsov@yandex-team.ru>
On 31/10/25 20:02, Vladimir Sementsov-Ogievskiy wrote:
> QEMU_HEXDUMP_LINE_WIDTH calculation doesn't correspond to
> qemu_hexdump_line(). This leads to last line of the dump (when
> length is not multiply of 16) has badly aligned ASCII part.
>
> Let's calculate length the same way.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
> ---
> util/hexdump.c | 38 ++++++++++++++++++++++++--------------
> 1 file changed, 24 insertions(+), 14 deletions(-)
>
> diff --git a/util/hexdump.c b/util/hexdump.c
> index f29ffceb74..7cfc547261 100644
> --- a/util/hexdump.c
> +++ b/util/hexdump.c
> @@ -22,6 +22,19 @@ static inline char hexdump_nibble(unsigned x)
> return (x < 10 ? '0' : 'a' - 10) + x;
> }
>
> +static size_t hexdump_line_length(size_t buf_len, size_t unit_len,
> + size_t block_len)
> +{
> + size_t est = buf_len * 2;
> + if (unit_len) {
> + est += buf_len / unit_len;
> + }
> + if (block_len) {
> + est += buf_len / block_len;
> + }
> + return est;
> +}
> void qemu_hexdump(FILE *fp, const char *prefix,
> const void *bufptr, size_t size)
> {
> - g_autoptr(GString) str = g_string_sized_new(QEMU_HEXDUMP_LINE_WIDTH + 1);
> + int width = hexdump_line_length(QEMU_HEXDUMP_LINE_BYTES,
size_t
> + QEMU_HEXDUMP_UNIT,
> + QEMU_HEXDUMP_BLOCK);
> + g_autoptr(GString) str = g_string_sized_new(width + 1);
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2025-10-31 20:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 19:02 [PATCH v2 0/2] util/hexdump: fix QEMU_HEXDUMP_LINE_WIDTH logic Vladimir Sementsov-Ogievskiy
2025-10-31 19:02 ` [PATCH v2 1/2] " Vladimir Sementsov-Ogievskiy
2025-10-31 20:54 ` Philippe Mathieu-Daudé [this message]
2025-10-31 20:59 ` Philippe Mathieu-Daudé
2025-10-31 19:02 ` [PATCH v2 2/2] tests/unit: add unit test for qemu_hexdump() Vladimir Sementsov-Ogievskiy
2025-10-31 20:54 ` Philippe Mathieu-Daudé
2025-10-31 20:56 ` [PATCH v2 0/2] util/hexdump: fix QEMU_HEXDUMP_LINE_WIDTH logic Philippe Mathieu-Daudé
2025-10-31 21:11 ` Philippe Mathieu-Daudé
2025-11-01 9:55 ` Vladimir Sementsov-Ogievskiy
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=d0f6aa76-08c6-4630-927e-358c8f81f383@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
/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).