linux-kernel - Re: [PATCH] fail kernel compilation in case of unresolved symbols (v2)

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: <20060907110513.GA22319@aepfle.de>
Date:	Thu, 7 Sep 2006 13:05:13 +0200
From:	Olaf Hering <olaf@...fle.de>
To:	Kirill Korotaev <dev@...nvz.org>
Cc:	Andrew Morton <akpm@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrey Mirkin <amirkin@...ru>, devel@...nvz.org,
	mikpe@...uu.se, sam@...nborg.org, bunk@...sta.de
Subject: Re: [PATCH] fail kernel compilation in case of unresolved symbols (v2)

On Thu, Sep 07, Kirill Korotaev wrote:

> At stage 2 modpost utility is used to check modules.
> In case of unresolved symbols modpost only prints warning.
> 
> IMHO it is a good idea to fail compilation process in case of
> unresolved symbols (at least in modules coming with kernel),
> since usually such errors are left unnoticed, but kernel
> modules are broken.

It clearly depends on the context. An unimportant dvb module may have
unresolved symbols, but the drivers for your root filesystem should
rather not have unresolved symbols.

Better leave the current default, your patch seems to turn an unresolved
symbol with "unknown importance" into a hard error.
-
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/