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 for Android: free password hash cracker in your pocket

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

Message-Id: <200705271339.36045.ak@suse.de>
Date:	Sun, 27 May 2007 13:39:35 +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


> The whole purpose with __init and friends are the possibility to drop
> the .init.text (+ .init.data) section when the kernel is up and running.

I know what they do, you don't need to repeatedly reexplain them.

My point was just that in all the __init/__initdata warnings I recently fixed
personally there wasn't a single one that wasn't a false positive and frankly I don't
see any sign of them really showing real bugs. Basically effort:gain doesn't
seem to be well balanced here.

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