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: <45003985.7060304@sw.ru>
Date:	Thu, 07 Sep 2006 19:23:49 +0400
From:	Kirill Korotaev <dev@...ru>
To:	Olaf Hering <olaf@...fle.de>
CC:	Adrian Bunk <bunk@...sta.de>, Kirill Korotaev <dev@...nvz.org>,
	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
Subject: Re: [PATCH] fail kernel compilation in case of unresolved symbols
 (v2)

Olaf Hering wrote:
> On Thu, Sep 07, Adrian Bunk wrote:
> 
> 
>>If any module shipped with the kernel has in any configuration 
>>unresolved symbols that's a bug that should be reported, not ignored.
> 
> 
> Yes, but on request when building the package. Not per default.
> I probably missed the reason why this is now suddenly a problem.
It is not that sudden at all. I experienced this problem many times so far
and working with a build system came to the idea of failing
builds when there are unresolved symbols.

I'm pretty sure that having this patch in mainstream
will make unresolved symbols a rare problem as many of them will be fixed soon.
So I'm pretty agree with Adrian that modules with unresolved symbols is a bug
and it MUST be fixed.
I would be very much interested to hear Andrew opinion on this as
he probably makes kernels even more often than any of us :)

Thanks,
Kirill

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