From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] util/hexdump: fix QEMU_HEXDUMP_LINE_WIDTH logic
Date: Mon, 8 Sep 2025 15:51:34 +0100 [thread overview]
Message-ID: <aL7tdmmT0ZEVZ1qb@redhat.com> (raw)
In-Reply-To: <20250905142006.2230345-1-vsementsov@yandex-team.ru>
On Fri, Sep 05, 2025 at 05:20:06PM +0300, 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(-)
Would you mind also adding a test to tests/unit/test-cutils.c
to show the correctness, as this is a nice standalone func
we ought to be unit testing.
>
> 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;
> +}
> +
> GString *qemu_hexdump_line(GString *str, const void *vbuf, size_t len,
> size_t unit_len, size_t block_len)
> {
> @@ -30,14 +43,8 @@ GString *qemu_hexdump_line(GString *str, const void *vbuf, size_t len,
>
> if (str == NULL) {
> /* Estimate the length of the output to avoid reallocs. */
> - size_t est = len * 2;
> - if (unit_len) {
> - est += len / unit_len;
> - }
> - if (block_len) {
> - est += len / block_len;
> - }
> - str = g_string_sized_new(est + 1);
> + str = g_string_sized_new(hexdump_line_length(len, unit_len, block_len)
> + + 1);
> }
>
> for (u = 0, b = 0; len; u++, b++, len--, buf++) {
> @@ -76,13 +83,16 @@ static void asciidump_line(char *line, const void *bufptr, size_t len)
> }
>
> #define QEMU_HEXDUMP_LINE_BYTES 16
> -#define QEMU_HEXDUMP_LINE_WIDTH \
> - (QEMU_HEXDUMP_LINE_BYTES * 2 + QEMU_HEXDUMP_LINE_BYTES / 4)
> +#define QEMU_HEXDUMP_UNIT 1
> +#define QEMU_HEXDUMP_BLOCK 4
>
> 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,
> + QEMU_HEXDUMP_UNIT,
> + QEMU_HEXDUMP_BLOCK);
> + g_autoptr(GString) str = g_string_sized_new(width + 1);
> char ascii[QEMU_HEXDUMP_LINE_BYTES + 1];
> size_t b, len;
>
> @@ -90,11 +100,11 @@ void qemu_hexdump(FILE *fp, const char *prefix,
> len = MIN(size - b, QEMU_HEXDUMP_LINE_BYTES);
>
> g_string_truncate(str, 0);
> - qemu_hexdump_line(str, bufptr + b, len, 1, 4);
> + qemu_hexdump_line(str, bufptr + b, len,
> + QEMU_HEXDUMP_UNIT, QEMU_HEXDUMP_BLOCK);
> asciidump_line(ascii, bufptr + b, len);
>
> - fprintf(fp, "%s: %04zx: %-*s %s\n",
> - prefix, b, QEMU_HEXDUMP_LINE_WIDTH, str->str, ascii);
> + fprintf(fp, "%s: %04zx: %-*s %s\n", prefix, b, width, str->str, ascii);
> }
>
> }
> --
> 2.48.1
>
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 :|
next prev parent reply other threads:[~2025-09-08 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 14:20 [PATCH] util/hexdump: fix QEMU_HEXDUMP_LINE_WIDTH logic Vladimir Sementsov-Ogievskiy
2025-09-08 14:51 ` Daniel P. Berrangé [this message]
2025-09-08 16:03 ` Vladimir Sementsov-Ogievskiy
2025-09-09 14:20 ` Ján Tomko
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=aL7tdmmT0ZEVZ1qb@redhat.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.