[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56e1b5710902050250u244a7499k90ad1825ee85bbad@mail.gmail.com>
Date: Thu, 5 Feb 2009 11:50:02 +0100
From: Floris Kraak <randakar@...il.com>
To: Andreas Schwab <schwab@...e.de>
Cc: Roland Dreier <rdreier@...co.com>,
Robert Hancock <hancockrwd@...il.com>,
Sam Ravnborg <sam@...nborg.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Trivial Patch Monkey <trivial@...nel.org>
Subject: Re: [PATCH] Kbuild: Disable the -Wformat-security gcc flag
On Thu, Feb 5, 2009 at 11:27 AM, Andreas Schwab <schwab@...e.de> wrote:
> Floris Kraak <randakar@...il.com> writes:
>
>> Example:
>>
>> kernel/power/main.c:717: warning: format not a string literal and no
>> format arguments
>>
>> This complains about:
>> ..
>> if (!rtc) {
>> printk(warn_no_rtc);
>> goto done;
>> }
>> ..
>>
>> So what is this "warn_no_rtc" thing?
>>
>> static char warn_no_rtc[] __initdata =
>> KERN_WARNING "PM: no wakealarm-capable RTC driver is ready\n";
>
> Does it help to make it const?
>
>> That's pretty much GCC failing to recognize that the format is a
>> string literal and then complaining that it isn't.
>
> Since it's a non-const variable it cannot be a string literal.
>
kernel/power/main.c:698: error: warn_no_rtc causes a section type conflict
Nice try ;-)
Replacing __initdata with __devinitconst sounded like it might solve
things ( - http://mail.nl.linux.org/kernelnewbies/2008-02/msg00042.html,
interesting reading) but alas, the warning persists.
(apologies to Andreas for the resend)
Regards,
Floris
---
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety."
-- Ben Franklin
"The course of history shows that as a government grows, liberty
decreases."
-- Thomas Jefferson
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists