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-next>] [day] [month] [year] [list]
Message-ID: <35a82d00610161135t3d65bf2ei46631e69bf6f7f12@mail.gmail.com>
Date:	Mon, 16 Oct 2006 11:35:13 -0700
From:	"Scott Baker" <smbaker@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: exported module symbols and warnings

Hello,

I'm developing a pair of kernel modules. One module needs to export a
symbol that will be used by the second module. I'm doing this by using
EXPORT_SYMBOL(MySymbol) in the first module and declaring the symbol
as extern in the second module. It works fine.

However, there are a couple of warnings that I'm trying to clean up.
The first is when building the second module (the one that uses the
symbol). It is: "*** Warning: "MySymbol" [filename] undefined!"

The second warning occurs when insmod'ing the second module. It is:
"no version for "MySymbol" found: kernel tainted."

Can someone point me in the right direction? The modules are behaving
fine, but the warning messages are a bit unsightly.

I'm running RHEL4, kernel version 2.6.9-42.

Thanks,
Scott
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ