From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Tilman Schmidt <tilman@imap.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_PROVE_RCU breaks proprietary modules (rcu_lock_map)
Date: Mon, 29 Mar 2010 08:09:46 -0700 [thread overview]
Message-ID: <20100329150946.GB2569@linux.vnet.ibm.com> (raw)
In-Reply-To: <4BA689EA.4050102@imap.cc>
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
next prev parent reply other threads:[~2010-03-29 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 21:04 CONFIG_PROVE_RCU breaks proprietary modules (rcu_lock_map) Tilman Schmidt
2010-03-29 15:09 ` Paul E. McKenney [this message]
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=20100329150946.GB2569@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tilman@imap.cc \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.