linux-kernel - Re: [PATCH v3.1] kbuild: implement several W= levels

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]

Date:	Thu, 28 Apr 2011 18:24:46 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	Valdis.Kletnieks@...edu
Cc:	Borislav Petkov <bp@...en8.de>, Sam Ravnborg <sam@...nborg.org>,
	linux-kbuild <linux-kbuild@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>
Subject: Re: [PATCH v3.1] kbuild: implement several W= levels

On 28.4.2011 02:25, Valdis.Kletnieks@...edu wrote:
> On Wed, 27 Apr 2011 13:35:13 +0200, Borislav Petkov said:
>
>> If we do this inclusive, then W=2 dumps the, let's call it, level 1
>> _plus_ the new level 2 warnings, polluting the output with something
>> I've already seen, but only partially. And then I start to think, did
>> I see this one already, didn't I, which was it? By the time you enable
>> W=3, the output becomes pretty useless. For example, W=3 generates 190+
>> MB logfile here only with level 3 warnings. Now imagine all 3 levels
>> combined.
>
> If each level is averaging 10x the previous level, then all 3 levels will only be 11%
> bigger, or 211MB.
>
> You *really* want to get *all* the warnings - quite often, you'll be looking
> at a set of 15 or 20 level-3 warnings.  And if you had the Level-2's in there as
> well, you'd immediately realize that the single level-2 was the real root-cause
> of all the cascating warnings.

How about W=12 for level 1 and 2 warnings and W=123 for all levels?

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