linux-kernel - Re: Announce: gcc bogus warning repository

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1159729390.24767.16.camel@c-67-180-230-165.hsd1.ca.comcast.net>
Date:	Sun, 01 Oct 2006 12:03:10 -0700
From:	Daniel Walker <dwalker@...sta.com>
To:	Al Viro <viro@....linux.org.uk>
Cc:	Jeff Garzik <jeff@...zik.org>, Andrew Morton <akpm@...l.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Announce: gcc bogus warning repository

On Sun, 2006-10-01 at 20:00 +0100, Al Viro wrote:
> On Sun, Oct 01, 2006 at 11:58:33AM -0700, Daniel Walker wrote:
> > On Sun, 2006-10-01 at 14:45 -0400, Jeff Garzik wrote:
> > 
> > > That doesn't address my question at all.
> > 
> > Did you have a question?
> > 
> > > If there is no difference between real non-init bugs and bogus warnings, 
> > > then a config option doesn't make any difference at all, does it?  Real 
> > > bugs are still hidden either way:  if the warnings are turned on, the 
> > > bugs are lost in the noise.  if the warnings are turned off, the bugs 
> > > are completely hidden.
> > 
> > If you turn the warnings on, at least you have a chance to see a warning
> > even if it's mixed with others.
> 
> And that's better than the current situation in which respects, exactly?

Seeing the warnings is the current situation.

Daniel

-
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/