From: Floris Kraak <randakar@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
WANG Cong <amwang@redhat.com>,
Jaswinder Singh Rajput <jaswinderrajput@gmail.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Frans Pop <elendil@planet.nl>, maximilian attems <max@stro.at>,
Tim Abbott <tabbott@ksplice.com>,
Paul Mundt <lethal@linux-sh.org>
Subject: Re: [GIT] kbuild fixes
Date: Fri, 3 Jul 2009 23:53:58 +0200 [thread overview]
Message-ID: <56e1b5710907031453i75066006p8a72c19a65d28efe@mail.gmail.com> (raw)
In-Reply-To: <20090703214309.GA15265@uranus.ravnborg.org>
On Fri, Jul 3, 2009 at 11:43 PM, Sam Ravnborg<sam@ravnborg.org> wrote:
>
> - disabling of -Wformat-security
> We looked at it and 'fixing' the warnings was not pleasant
The alternative is roughly 136 'trivial' patches to shut them all up*
and one to turn this flag on unconditionally to prevent hackers from
adding more of them after that ;-)
The alternative to *that* is improving on this silly flag:
- Either finding some way to teach GCC how to not emit warnings about
usage that is entirely sane.
- Or finding some way to teach some other build tool to catch unsafe
usage without polluting the build with false positives.
Take your pick.
*) While I can't give you 100% certainty about every warning I know
for a fact the vast majority of the warnings at least consists of
false positives so there'd be no other benefit from them except a
quieter kernel build on certain distro's ;-)
Regards,
Floris
---
'Or lawyers may say, “But if I decline, someone else will do it. So
what is gained?” My reply: “Let someone else do it. But not you. Honor
is personal. Worry about yourself. You don’t get a pass from moral
responsibility because you acted for a client.”
That’s the first lesson I would offer, aimed at lawyers. A second
lesson, aimed at all, is this: Keep ready your capacity for outrage.
This is very important. Next to the vote, outrage is the one response
each of us can contribute. Outrage is how honor must confront
dishonor. If we lose the capacity for outrage, we are in serious
trouble. '
--- Stephen Gillers
next prev parent reply other threads:[~2009-07-03 21:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 21:43 Sam Ravnborg
2009-07-03 21:53 ` Floris Kraak [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-07 15:53 Michal Marek
2010-06-11 13:59 Michal Marek
2009-07-20 20:35 Sam Ravnborg
2009-06-20 11:44 Sam Ravnborg
2009-05-05 19:04 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=56e1b5710907031453i75066006p8a72c19a65d28efe@mail.gmail.com \
--to=randakar@gmail.com \
--cc=amwang@redhat.com \
--cc=elendil@planet.nl \
--cc=jaswinderrajput@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max@stro.at \
--cc=penberg@cs.helsinki.fi \
--cc=sam@ravnborg.org \
--cc=tabbott@ksplice.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®