All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Floris Kraak <randakar@gmail.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Trivial Patch Monkey <trivial@kernel.org>
Subject: Re: [PATCH] Kbuild: Disable the -Wformat-security gcc flag
Date: Wed, 04 Feb 2009 17:48:42 -0600	[thread overview]
Message-ID: <498A295A.4090008@gmail.com> (raw)
In-Reply-To: <adavdrplty2.fsf@cisco.com>

Roland Dreier wrote:
>  > Before judging on this patch could you please post what warning it
>  > triggers and one or a few patches to fix some of them.
> 
> The warnings are things like:
> 
>     init/main.c: In function 'start_kernel':
>     init/main.c:557: warning: format not a string literal and no format arguments
> 
> where the patch to fix this would be:
> 
> diff --git a/init/main.c b/init/main.c
> index 8442094..78fc0d8 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -554,7 +554,7 @@ asmlinkage void __init start_kernel(void)
>  	boot_cpu_init();
>  	page_address_init();
>  	printk(KERN_NOTICE);
> -	printk(linux_banner);
> +	printk("%s", linux_banner);
>  	setup_arch(&command_line);
>  	mm_init_owner(&init_mm, &init_task);
>  	setup_command_line(command_line);
> 
> with the impact:
> 
> add/remove: 0/0 grow/shrink: 1/0 up/down: 7/0 (7)
> function                                     old     new   delta
> start_kernel                                 689     696      +7

Just how many of these warnings are showing up? In the cases you posted 
it's presumably no problem, but if the string could either a) be 
potentially set by a malicious user or b) accidentally contain printk 
format characters then this code has a risk that things could blow up..

  reply	other threads:[~2009-02-04 23:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 14:28 [PATCH] Kbuild: Disable the -Wformat-security gcc flag Floris Kraak
2009-02-04 22:14 ` Sam Ravnborg
2009-02-04 22:26   ` Roland Dreier
2009-02-04 23:48     ` Robert Hancock [this message]
2009-02-05  6:37       ` Roland Dreier
2009-02-05  8:26         ` Floris Kraak
2009-02-05 10:15           ` Floris Kraak
2009-02-05 10:27             ` Andreas Schwab
2009-02-05 10:50               ` Floris Kraak
2009-02-05 21:52               ` Roland Dreier
2009-02-10 21:11           ` Kyle Moffett
2009-02-10 21:56             ` Floris Kraak
2009-02-10 20:24     ` Pavel Machek
2009-02-10 21:48       ` Floris Kraak
2009-05-15 10:23 ` Pekka Enberg
2009-05-15 13:28   ` Floris Kraak
2009-05-15 20:42     ` Pekka Enberg
2009-05-15 22:09       ` Floris Kraak
2009-06-14 20:50     ` Sam Ravnborg
2009-06-15  5:54       ` Pekka J Enberg
2009-06-15  8:02         ` Floris Kraak
2009-06-26 22:15         ` Sam Ravnborg

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=498A295A.4090008@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randakar@gmail.com \
    --cc=rdreier@cisco.com \
    --cc=sam@ravnborg.org \
    --cc=trivial@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 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.