linux-kernel - Re: [RFC PATCH] kbuild: silence section mismatch warnings

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: <8210B049-55BD-409F-8A5E-EC5E1C365604@kernel.crashing.org>
Date:	Fri, 11 May 2007 16:22:28 -0500
From:	Kumar Gala <galak@...nel.crashing.org>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] kbuild: silence section mismatch warnings


On May 11, 2007, at 4:08 PM, Sam Ravnborg wrote:

> ----- Forwarded message from Sam Ravnborg <sam@...nborg.org> -----
>
> Forgot lkml in first mail...
>
> 	Sam
>
> Subject: [RFC PATCH] kbuild: silence section mismatch warnings
> From: Sam Ravnborg <sam@...nborg.org>
> Date: Fri, 11 May 2007 23:03:46 +0200
> User-Agent: Mutt/1.4.2.1i
> To: Chris Wedgwood <cw@...f.org>, Andrew Morton <akpm@...l.org>,
> 	"David S. Miller" <davem@...hat.com>,
> 	Russell King <rmk@....linux.org.uk>,
> 	Satyam Sharma <satyam.sharma@...il.com>
> Cc: sam@...nborg.org
>
> Following patch allow us in specific places to silence section  
> mismatch warnings.
> There is a few legitime places that modpost does not yet recognize  
> where
> reference from .text to .init.text (likewise for data) are legitime.
> This allow us to spot the few places and annotate them so we do not
> get false warnings that in the end will let real warnings pass.
>
> The annotation is simple to grep for so revieing all uses in a few
> months time are trivial. It is assumed that a few places will
> use this to shut up the warning as replacement for the real fix.
> But these cases are esay to spot and to fix up.

Its unclear if you expect that some things will be tagged  
__init_refok/__initdata_refok forever or if we'll find some way to  
fix/change the code so the things tagged no longer need it.

> With this and the following two patches I have a section mismatch free
> build.
> The plan is that a section mismatch soon will graduate from a  
> warning to an error.
> This will hurt a few drives but then they have an incentive to fix  
> it up.
>
> Comments welcome.

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