All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony@xenproject.org>
To: Alejandro Vallejo <alejandro.garciavallejo@amd.com>,
	Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Anthony PERARD <anthony.perard@vates.tech>,
	Xen-devel <xen-devel-bounces@lists.xenproject.org>
Subject: Re: [PATCH] xenalyze: correct symbol name length fscanf() specifier
Date: Thu, 31 Jul 2025 11:37:11 +0200	[thread overview]
Message-ID: <aIs5R_ttIOGTApqj@l14> (raw)
In-Reply-To: <DBNUR2PNKJKP.677MC6QFT97J@amd.com>

On Mon, Jul 28, 2025 at 07:08:46PM +0200, Alejandro Vallejo wrote:
> On Mon Jul 28, 2025 at 5:52 PM CEST, Jan Beulich wrote:
> > SYMBOL_NAME_SIZE is 124, not 128. Use the symbolic name there as well,
> > to avoid any disconnect.
> >
> > While there correct indentation on the following line as well.
> >
> > Coverity ID: 1659391
> > Signed-off-by: Jan Beulich <jbeulich@suse.com>
> > ---
> > There's no useful Fixes: tag; the code was imported from HG this way
> > about 10 years ago.
> >
> > --- a/tools/xentrace/xenalyze.c
> > +++ b/tools/xentrace/xenalyze.c
> > @@ -321,11 +321,10 @@ void parse_symbol_file(char *fn) {
> >              (*p)->next=NULL;
> >          }
> >  
> > -        /* FIXME -- use SYMBOL_NAME_SIZE */
> >          /* FIXME -- use regexp.  This won't work for symbols with spaces (yes they exist) */
> >          (*p)->symbols[(*p)->count].addr = 0xDEADBEEF;
> > -        if ( fscanf(symbol_file, "%llx %128s",
> > -               &(*p)->symbols[(*p)->count].addr,
> > +        if ( fscanf(symbol_file, "%llx %" STR(SYMBOL_NAME_SIZE) "s",
> 
> nit: A comment at the #define stating it's used this way would prevent future
> "oops" situations when/if someone tries to do (e.g) "#define SYMBOL_NAME_SIZE (1
> << 4)"
> 
> Though arguably that would cause a compile-time error anyway (except perhaps
> an octal literal?), so meh. With or without the adjustment:
> 
>   Reviewed-by: Alejandro Vallejo <alejandro.garciavallejo@amd.com>

Acked-by: Anthony PERARD <anthony.perard@vates.tech>

Thanks,

-- 
Anthony PERARD


      reply	other threads:[~2025-07-31  9:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 15:52 [PATCH] xenalyze: correct symbol name length fscanf() specifier Jan Beulich
2025-07-28 17:08 ` Alejandro Vallejo
2025-07-31  9:37   ` Anthony PERARD [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=aIs5R_ttIOGTApqj@l14 \
    --to=anthony@xenproject.org \
    --cc=alejandro.garciavallejo@amd.com \
    --cc=anthony.perard@vates.tech \
    --cc=jbeulich@suse.com \
    --cc=xen-devel-bounces@lists.xenproject.org \
    --cc=xen-devel@lists.xenproject.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 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.