From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Tilman Schmidt <tilman@imap.cc>, linux-kernel@vger.kernel.org
Subject: Re: CONFIG_PROVE_RCU breaks proprietary modules (rcu_lock_map)
Date: Sun, 20 Jun 2010 08:16:05 -0700 [thread overview]
Message-ID: <20100620151605.GA2396@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100617103747.GZ20317@bombadil.infradead.org>
On Thu, Jun 17, 2010 at 06:37:47AM -0400, Kyle McMartin wrote:
> On Mon, Mar 29, 2010 at 11:40:59AM -0700, Paul E. McKenney wrote:
> > > > 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! ;-)
> >
>
> Hi Paul,
>
> (Sorry I didn't bring this up until now.)
>
> I don't really have any sympathy for people who use that crud, but from
> my POV it's going to generate some grief. Fedora builds rawhide with a
> lot of debugging options enabled in order to try and hit issues early
> before kernels release.
>
> A few weeks ago, I noticed a report that PROVE_RCU was breaking some
> non-GPL junk. Digging a bit further, I noticed quite a number of more
> reports of this.
>
> Is there any chances you could reconsider this? Otherwise I'll probably
> disable the option in Fedora's debug kernels as well if I continue to
> see confused users.
Hello, Kyle,
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?
Thanx, Paul
next prev parent reply other threads:[~2010-06-20 15:16 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
2010-03-29 18:40 ` Paul E. McKenney
2010-06-17 10:37 ` Kyle McMartin
2010-06-20 15:16 ` Paul E. McKenney [this message]
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=20100620151605.GA2396@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=kyle@mcmartin.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox