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]

Date:	Sun, 24 Sep 2006 23:48:51 +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:47:40AM +0200, Sam Ravnborg wrote:
> > That's out of 25 targets.  The only variants that do _NOT_ trigger are
> > amd64, amd64-UP, i386 and uml-amd64.
> 
> How many of these ougth to be fixed then?

In theory - all of them.  Right now that's just plain not feasible...

> > 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...
> OK. Will include it in next round of kbuild updates.

BTW, an alternative would be to stop unconditionally after full set of checks
and not bother with .mod.o/.ko at all.  _Not_ as a default, of course...
-
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/