From: Petr Mladek <pmladek@suse.com>
To: Nicolas Iooss <nicolas.iooss_linux@m4x.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] printk: add __printf attributes to internal functions
Date: Mon, 22 May 2017 17:22:11 +0200 [thread overview]
Message-ID: <20170522152211.GF12489@pathway.suse.cz> (raw)
In-Reply-To: <20170520091853.26643-1-nicolas.iooss_linux@m4x.org>
On Sat 2017-05-20 11:18:53, Nicolas Iooss wrote:
> When compiling with -Wsuggest-attribute=format, gcc complains that some
> functions in kernel/printk/printk_safe.c transmit their argument to
> printf-like functions without having a printf attribute. Silence these
> warnings by adding relevant __printf attributes.
>
> Signed-off-by: Nicolas Iooss <nicolas.iooss_linux@m4x.org>
> ---
> kernel/printk/printk_safe.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/printk/printk_safe.c b/kernel/printk/printk_safe.c
> index 033e50a7d706..2e27a31941f4 100644
> --- a/kernel/printk/printk_safe.c
> +++ b/kernel/printk/printk_safe.c
> @@ -80,8 +80,8 @@ static void queue_flush_work(struct printk_safe_seq_buf *s)
> * happen, printk_safe_log_store() will notice the buffer->len mismatch
> * and repeat the write.
> */
> -static int printk_safe_log_store(struct printk_safe_seq_buf *s,
> - const char *fmt, va_list args)
> +static __printf(2, 0) int printk_safe_log_store(struct printk_safe_seq_buf *s,
> + const char *fmt, va_list args)
> {
> int add;
> size_t len;
> @@ -299,7 +299,7 @@ void printk_safe_flush_on_panic(void)
> * one writer running. But the buffer might get flushed from another
> * CPU, so we need to be careful.
> */
> -static int vprintk_nmi(const char *fmt, va_list args)
> +static __printf(1, 0) int vprintk_nmi(const char *fmt, va_list args)
There is one more variant of this function used when CONFIG_PRINTK_NMI
is not defined. Feel free to send updated patch as a reply. Or I could
add this trivial change when pushing this patch to printk.git if nobody
complains.
Otherwise, the patch looks fine to me. Therefore with patching the other
vprintk_nmi() variant:
Acked-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
next prev parent reply other threads:[~2017-05-22 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 9:18 [PATCH 1/1] printk: add __printf attributes to internal functions Nicolas Iooss
2017-05-22 2:48 ` Sergey Senozhatsky
2017-05-22 15:22 ` Petr Mladek [this message]
2017-05-24 5:49 ` [PATCH v2 " Nicolas Iooss
2017-05-25 11:29 ` Petr Mladek
2017-05-25 12:02 ` Sergey Senozhatsky
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=20170522152211.GF12489@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.iooss_linux@m4x.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
/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