From: Denis Kirjanov <dkirjanov@suse.de>
To: David Ahern <dsahern@kernel.org>,
Denis Kirjanov <kirjanov@gmail.com>,
stephen@networkplumber.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] ss: fix the compiler warning
Date: Mon, 11 Mar 2024 17:20:31 +0300 [thread overview]
Message-ID: <4c58ab4f-e1c8-4267-a4ba-518986d03125@suse.de> (raw)
In-Reply-To: <cd48d41f-b9ee-4906-a806-760284a3eeb4@kernel.org>
On 3/9/24 21:22, David Ahern wrote:
> On 3/7/24 3:53 AM, Denis Kirjanov wrote:
>> the patch fixes the following compiler warning:
>>
>> ss.c:1064:53: warning: format string is not a string literal [-Wformat-nonliteral]
>> len = vsnprintf(pos, buf_chunk_avail(buffer.tail), fmt, _args);
>> ^~~
>> 1 warning generated.
>> LINK ss
>>
>> Fixes: e3ecf0485 ("ss: pretty-print BPF socket-local storage")
>> Signed-off-by: Denis Kirjanov <dkirjanov@suse.de>
>> ---
>> misc/ss.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/misc/ss.c b/misc/ss.c
>> index 87008d7c..038905f3 100644
>> --- a/misc/ss.c
>> +++ b/misc/ss.c
>> @@ -1042,6 +1042,7 @@ static int buf_update(int len)
>> }
>>
>> /* Append content to buffer as part of the current field */
>> +__attribute__((format(printf, 1, 0)))
>> static void vout(const char *fmt, va_list args)
>> {
>> struct column *f = current_field;
>
> The error message does not align with the change - and it does not fix
> the warning.
since vout is not a variadic arguments function I put 0 into the 3rd argument since we
already have a check in out function.
doc[0] states that:
"For functions where the arguments are not available to be checked (such as vprintf),
specify the third parameter as zero.
In this case the compiler only checks the format string for consistency."
[0]: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html
>
> pw-bot: cr
>
prev parent reply other threads:[~2024-03-11 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 10:53 [PATCH iproute2-next] ss: fix the compiler warning Denis Kirjanov
2024-03-09 18:22 ` David Ahern
2024-03-09 19:30 ` Stephen Hemminger
2024-03-11 14:20 ` Denis Kirjanov [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=4c58ab4f-e1c8-4267-a4ba-518986d03125@suse.de \
--to=dkirjanov@suse.de \
--cc=dsahern@kernel.org \
--cc=kirjanov@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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.