public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: linux-kernel@vger.kernel.org
Subject: CONFIG_PROVE_RCU breaks proprietary modules (rcu_lock_map)
Date: Sun, 21 Mar 2010 22:04:42 +0100	[thread overview]
Message-ID: <4BA689EA.4050102@imap.cc> (raw)

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

             reply	other threads:[~2010-03-21 21:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-21 21:04 Tilman Schmidt [this message]
2010-03-29 15:09 ` CONFIG_PROVE_RCU breaks proprietary modules (rcu_lock_map) Paul E. McKenney
2010-03-29 17:53   ` Tilman Schmidt
2010-03-29 18:40     ` Paul E. McKenney
2010-06-17 10:37       ` Kyle McMartin
2010-06-20 15:16         ` Paul E. McKenney
2010-06-21 10:14           ` Kyle McMartin
2010-06-21 16:46             ` Paul E. McKenney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BA689EA.4050102@imap.cc \
    --to=tilman@imap.cc \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox