linux-kernel - Re: [PATCH] x86: fix section mismatch warnings in mtrr

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: <200705271156.22098.ak@suse.de>
Date:	Sun, 27 May 2007 11:56:21 +0200
From:	Andi Kleen <ak@...e.de>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Indan Zupancic <indan@....nu>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	Andrey Borzenkov <arvidjaar@...l.ru>,
	linux-kernel@...r.kernel.org, Bernhard Walle <bwalle@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] x86: fix section mismatch warnings in mtrr


> 
> So section mismatch warnings are more about catching sloopy usage of __init than it is to
> catch potential kernel oopesen. But the latter is a nice side effect that is appreciated.

My point was that I cannot recall a single real oops bug found by the compile
time checking.

We had a few in the past, but since we poison init data after boot they all tended
to be found quickly anyways.

But the warnings just seem to require endless changes and bogus changes
(randomly moving code which was actually ok because it only called 
in the init case).

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