public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Cengiz Can <cengiz@kernel.wtf>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools: perf: fix augmented syscall format warning
Date: Tue, 14 Jan 2020 12:47:18 -0300	[thread overview]
Message-ID: <20200114154718.GC20569@kernel.org> (raw)
In-Reply-To: <20200113174438.102975-1-cengiz@kernel.wtf>

Em Mon, Jan 13, 2020 at 08:44:39PM +0300, Cengiz Can escreveu:
> sockaddr related examples given in
> `tools/perf/examples/bpf/augmented_syscalls.c` almost always use `long`s
> to represent most of their fields.
> 
> However, `size_t syscall_arg__scnprintf_sockaddr(..)` has a `scnprintf`
> call that uses `"%#x"` as format string.
> 
> This throws a warning (whenever the syscall argument is `unsigned
> long`).
> 
> Added `l` identifier to indicate that the `arg->value` is an unsigned
> long.

arg->val is a 'unsigned long', so yeah, we can make that lx to make it
work in more places,

In fact it should be fallbacking to this, that does just like you did
here:

size_t syscall_arg__scnprintf_hex(char *bf, size_t size, struct syscall_arg *arg)
{
        return scnprintf(bf, size, "%#lx", arg->val);
}

It is in tools/perf/builtin-trace.c

Thanks,

-  Arnaldo
 
> Not sure about the complications of this with x86 though.
> 
> Signed-off-by: Cengiz Can <cengiz@kernel.wtf>
> ---
>  tools/perf/trace/beauty/sockaddr.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/perf/trace/beauty/sockaddr.c b/tools/perf/trace/beauty/sockaddr.c
> index 173c8f760763..e0c13e6a5788 100644
> --- a/tools/perf/trace/beauty/sockaddr.c
> +++ b/tools/perf/trace/beauty/sockaddr.c
> @@ -72,5 +72,5 @@ size_t syscall_arg__scnprintf_sockaddr(char *bf, size_t size, struct syscall_arg
>  	if (arg->augmented.args)
>  		return syscall_arg__scnprintf_augmented_sockaddr(arg, bf, size);
> 
> -	return scnprintf(bf, size, "%#x", arg->val);
> +	return scnprintf(bf, size, "%#lx", arg->val);
>  }
> --
> 2.24.1
> 

-- 

- Arnaldo

  reply	other threads:[~2020-01-14 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 17:44 [PATCH] tools: perf: fix augmented syscall format warning Cengiz Can
2020-01-14 15:47 ` Arnaldo Carvalho de Melo [this message]
2020-01-20  8:27 ` [tip: perf/core] perf beauty sockaddr: Fix " tip-bot2 for Cengiz Can

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=20200114154718.GC20569@kernel.org \
    --to=arnaldo.melo@gmail.com \
    --cc=cengiz@kernel.wtf \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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