linux-kernel - Re: Linux 2.6.19-rc4

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: <45477668.4070801@google.com>
Date:	Tue, 31 Oct 2006 08:14:32 -0800
From:	"Martin J. Bligh" <mbligh@...gle.com>
To:	Linus Torvalds <torvalds@...l.org>
CC:	Andrew Morton <akpm@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Jun'ichi Nomura" <j-nomura@...jp.nec.com>
Subject: Re: Linux 2.6.19-rc4

> But I've become innoculated against warnings, just because we have too 
> many of the totally useless noise about deprecation and crud, and ppc has 
> it's own set of bogus compiler-and-linker-generated warnings..
> 
> At some point we should get rid of all the "politeness" warnings, just 
> because they can end up hiding the _real_ ones.

Yay! Couldn't agree more. Does this mean you'll take patches for all the
uninitialized variable crap from gcc 4.x ?

> "pm_register is deprecated" etc - I get almost a hundred lines of warnings 
> in my default build (and half of those are sadly due to powerpc binutils, 
> that I can't do anythign about: "section .init.text exceeds stub group 
> size" etc, which is harmless _other_ than the fact that it helped hide the 
> real warnings just because I've grown too used to not looking too 
> closely).

Doesn't turning off CONFIG_PM_LEGACY fix those? it did for me.

M.

PS. I still think -Werror is a good plan. But I acknowledge that's
fairly extreme.
-
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/