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: <20071023172530.GA26345@uranus.ravnborg.org>
Date:	Tue, 23 Oct 2007 19:25:30 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	"Maciej W. Rozycki" <macro@...ux-mips.org>,
	Ralf Baechle <ralf@...ux-mips.org>,
	Franck Bui-Huu <vagabon.xyz@...il.com>,
	linux-arch@...r.kernel.org, linux-mips@...ux-mips.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Discardable strings for init and exit sections

> 
> As long as the modpost warnings are just warnings they will often be 
> missed at compile time.

The plans for the modpost warnings are more or less:
- Let all __init, __cpuinit, __meminit etc use dedicated sections
no matter the actual configuration.
Use ifdeffery in the .lds files to place stuff in the correct final
section.
Teach modpost about the illegal dependencies.

When we then are back to almost warning free with allmodconfig for
the most important platfroms (read: or in reality the ones I have a
tool-chain for and which care to make allmodconfig buildable in mainline)
then modpost will generate errors instead of warnings to force people
to fix all the NEW errors they introuduce.

A variable will convert the errors to warnings for use in certain situations.

But I am not familiar enough with ELF format to extend the current checking
as suggested by people a few times. Maybe someone else can assist here.

Comments?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ