linux-kernel - CONFIG_PROVE_RCU breaks proprietary modules (rcu_lock

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]

Date:	Sun, 21 Mar 2010 22:04:42 +0100
From:	Tilman Schmidt <tilman@...p.cc>
To:	linux-kernel@...r.kernel.org
Subject: CONFIG_PROVE_RCU breaks proprietary modules (rcu_lock_map)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I know there's not much sympathy for troubles with proprietary modules
here, but the following might save some trouble to kernel developers as
well as users forced to resort to proprietary drivers:

Setting the kernel configuration option PROVE_RCU creates a reference to
the GPL-exported global variable rcu_lock_map even in modules that do
not use RCU. In the case of non-GPL modules, this leads to a build
failure because of the license incompatibility.
(I did not find out where that reference comes from.)

So if building a proprietary module fails with the message:

FATAL: modpost: GPL-incompatible module <module> uses GPL-only symbol
'rcu_lock_map'

try rebuilding your kernel with the PROVE_RCU option disabled.

Hope it helps someone.

Tilman
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAkumieoACgkQQ3+did9BuFtC4gCggSE8DNVc8k9tasN7VOoQMR4G
IKUAnj+SkzZjmJQPmUScvaY4zP8hR19o
=2rDg
-----END PGP SIGNATURE-----
--
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/