All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_PROVE_RCU breaks proprietary modules (rcu_lock_map)
Date: Mon, 29 Mar 2010 19:53:59 +0200	[thread overview]
Message-ID: <4BB0E937.7070200@imap.cc> (raw)
In-Reply-To: <20100329150946.GB2569@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]

Am 29.03.2010 17:09 schrieb Paul E. McKenney:
> On Sun, Mar 21, 2010 at 10:04:42PM +0100, Tilman Schmidt wrote:
[...]
>> 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.

I agree completely. I just wanted to publish that fact because it seems
to be little known and can be quite a puzzler.

Thanks,
Tilman

-- 
Tilman Schmidt                    E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2010-03-29 17:57 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
2010-03-29 17:53   ` Tilman Schmidt [this message]
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=4BB0E937.7070200@imap.cc \
    --to=tilman@imap.cc \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    /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.