From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Alan Maguire <alan.maguire@oracle.com>, bpf@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bpf: add __printf() to for printf fmt strings
Date: Fri, 8 Dec 2023 17:26:13 +0000 [thread overview]
Message-ID: <948c34c3-bbbe-484c-892e-cd67abe3ce30@codethink.co.uk> (raw)
In-Reply-To: <8a713266-777f-099c-2eed-7ac13b7b72a6@oracle.com>
On 22/11/2023 16:44, Alan Maguire wrote:
> On 22/11/2023 13:36, Ben Dooks wrote:
>> The btf_seq_show() and btf_snprintf_show() take a printk format
>> string so add a __printf() to these two functions. This fixes the
>> following extended warnings:
>>
>> kernel/bpf/btf.c:7094:29: error: function ‘btf_seq_show’ might be a candidate for ‘gnu_printf’ format attribute [-Werror=suggest-attribute=format]
>> kernel/bpf/btf.c:7131:9: error: function ‘btf_snprintf_show’ might be a candidate for ‘gnu_printf’ format attribute [-Werror=suggest-attribute=format]
>>
>> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
>
> Looks good to me, thanks for fixing! Could also add a
>
> Fixes: eb411377aed9 ("bpf: Add bpf_seq_printf_btf helper")
>
> Reviewed-by: Alan Maguire <alan.maguire@oracle.com>
Thanks, looks like the test robot found some issues so will
go back and look at those as soon as I can.
>> ---
>> kernel/bpf/btf.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
>> index 15d71d2986d3..46c2e87c383d 100644
>> --- a/kernel/bpf/btf.c
>> +++ b/kernel/bpf/btf.c
>> @@ -7088,8 +7088,8 @@ static void btf_type_show(const struct btf *btf, u32 type_id, void *obj,
>> btf_type_ops(t)->show(btf, t, type_id, obj, 0, show);
>> }
>>
>> -static void btf_seq_show(struct btf_show *show, const char *fmt,
>> - va_list args)
>> +static __printf(2,0) void btf_seq_show(struct btf_show *show, const char *fmt,
>> + va_list args)
>> {
>> seq_vprintf((struct seq_file *)show->target, fmt, args);
>> }
>> @@ -7122,7 +7122,7 @@ struct btf_show_snprintf {
>> int len; /* length we would have written */
>> };
>>
>> -static void btf_snprintf_show(struct btf_show *show, const char *fmt,
>> +static __printf(2,0) void btf_snprintf_show(struct btf_show *show, const char *fmt,
>> va_list args)
>> {
>> struct btf_show_snprintf *ssnprintf = (struct btf_show_snprintf *)show;
>
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2023-12-08 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 13:36 [PATCH] bpf: add __printf() to for printf fmt strings Ben Dooks
2023-11-22 15:26 ` Daniel Borkmann
2023-11-22 16:44 ` Alan Maguire
2023-12-08 17:26 ` Ben Dooks [this message]
2023-11-23 3:16 ` kernel test robot
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=948c34c3-bbbe-484c-892e-cd67abe3ce30@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=alan.maguire@oracle.com \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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