linux-kernel - Re: [PATCH] module loader should not complain about unknown symbol

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:	Mon, 12 Nov 2007 17:59:53 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Jan Glauber <jang@...ux.vnet.ibm.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Pavel Emelyanov <xemul@...nvz.org>,
	Andi Kleen <andi@...stfloor.org>,
	Jon Masters <jonathan@...masters.org>
Subject: Re: [PATCH] module loader should not complain about unknown symbol

On Mon, Nov 12, 2007 at 02:18:27PM +0000, Jan Glauber wrote:
> If module A depends on module B and module B has not yet finished its
> init() the module loader may print a warning about an unknown symbol.
> 
> This happens if module B is still in state MODULE_STATE_COMING,
> as module A runs into resolve_symbol() for a symbol from module B.
> resolve_symbol() return 0 in that case and causes the warning.

I don't think that patch is a good idea. It points to a kernel problem of 
some sort that needs to be resolved. Making it fail silently is not
an improvement.

Also how else should the user know about "legitimate" (not caused by races)
unresolved symbols? 

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