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: <20100621101425.GA20317@bombadil.infradead.org>
Date:	Mon, 21 Jun 2010 06:14:26 -0400
From:	Kyle McMartin <kyle@...artin.ca>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	Kyle McMartin <kyle@...artin.ca>, Tilman Schmidt <tilman@...p.cc>,
	linux-kernel@...r.kernel.org
Subject: Re: CONFIG_PROVE_RCU breaks proprietary modules (rcu_lock_map)

On Sun, Jun 20, 2010 at 08:16:05AM -0700, Paul E. McKenney wrote:
> My kneejerk reaction is that PROVE_RCU is a developer tool, so I am
> OK with it not being set by default in Rawhide.  Or have you seen good
> value from (say) PROVE_LOCKING in Rawhide?
> 

Hi Paul,

I'm fine with this, we try to enable debug options in rawhide in order
to get the most out of bug reports/dmesgs that we can. We've definitely
spotted a lot of lockdep reports by having it enabled for general
desktop use cases (but as debugging has become more intensive, the perf
loss from having it enabled is more costly.)

I suspect we'll be OK with PROVE_RCU off though.

Thanks!

regards, Kyle
--
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/