Re: CONFIG_PROVE_RCU breaks proprietary modules (rcu_lock_map)

From: Paul E. McKenney
Date: Mon Mar 29 2010 - 11:09:54 EST


On Sun, Mar 21, 2010 at 10:04:42PM +0100, Tilman Schmidt wrote:
> -----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.

I am comfortable with PROVE_RCU being incompatible with non-GPL modules.
After all, it is only a debugging option, not intended for production use.

Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/