linux-kernel - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100329184059.GL2569@linux.vnet.ibm.com>
Date:	Mon, 29 Mar 2010 11:40:59 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Tilman Schmidt <tilman@...p.cc>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: CONFIG_PROVE_RCU breaks proprietary modules (rcu_lock_map)

On Mon, Mar 29, 2010 at 07:53:59PM +0200, Tilman Schmidt wrote:
> 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.

And I do very much appreciate your publicizing the solution!  ;-)

						Thanx, Paul
--
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/