linux-kernel - Re: [PATCH 18/28] kbuild: fail kernel compilation in case of unresolved module symbols

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: <20060924223643.GT29920@ftp.linux.org.uk>
Date:	Sun, 24 Sep 2006 23:36:43 +0100
From:	Al Viro <viro@....linux.org.uk>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	linux-kernel@...r.kernel.org, Kirill Korotaev <dev@...nvz.org>,
	Andrey Mirkin <amirkin@...ru>, Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH 18/28] kbuild: fail kernel compilation in case of unresolved module symbols

On Mon, Sep 25, 2006 at 12:35:34AM +0200, Sam Ravnborg wrote:
> On what architectures do you see lots of these warnings - maybe fixable?
> Otherwise I could do something like this:

Try allmodconfig someday...

aviro@icy:/usr/src/cross-kernel/volatile/work$ grep -l WARNING.*undefined ../logs/*/X4c
../logs/alpha-SMP/X4c
../logs/alpha/X4c
../logs/arm/X4c
../logs/armv/X4c
../logs/chestnut/X4c
../logs/frv/X4c
../logs/ia64/X4c
../logs/m32r/X4c
../logs/m68k/X4c
../logs/ppc/X4c
../logs/ppc44x/X4c
../logs/ppc64/X4c
../logs/s390/X4c
../logs/s390x/X4c
../logs/sparc32/X4c
../logs/sparc64/X4c
../logs/sun3/X4c
../logs/sun4/X4c
../logs/uml-i386/X4c

That's out of 25 targets.  The only variants that do _NOT_ trigger are
amd64, amd64-UP, i386 and uml-amd64.

I more or less agree with rationale behind making that default, but I'd
very much appreciate a way to override that.  For now I've just made the
-w line unconditional, but the fewer infrastructure patches I've to carry...
-
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/