public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Vandrovec <petr@vandrovec.name>
To: Valdis.Kletnieks@vt.edu
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add note that lockdep is not allowed with non-GPL modules
Date: Wed, 05 Jul 2006 04:54:11 +0200	[thread overview]
Message-ID: <44AB29D3.9090106@vandrovec.name> (raw)
In-Reply-To: <200607050247.k652lkaD006629@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu wrote:
> On Tue, 04 Jul 2006 23:20:53 +0200, Petr Vandrovec said:
> 
>>>Lock validor found a bug in NVidia driver, film at 11.
> 
> 
> It almost certainly didn't, as you have to do some major ugly and evil
> things to get the NVidia driver to build (it won't pass modpost if the
> kernel is built with lockdep due to the GPL-only exports that get sucked in).
> 
> 
>>I have no idea how NVidia managed to work around that problem, but 
>>VMware modules suddenly depend on this GPL-only symbol, although nothing 
>>in the module sources refers to lockdep (same sources which worked 
>>yesterday are being used).
> 
> It doesn't reference it directly - it gets sucked in via a #define.

VMware code is shoot down due to use of init_waitqueue_head().  It is 
now virtually GPL-only because it is inlined and uses GPL-only function 
lockdep_init_map :-(
						Petr

      reply	other threads:[~2006-07-05  2:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04 20:29 [PATCH] Add note that lockdep is not allowed with non-GPL modules Petr Vandrovec
2006-07-04 20:53 ` Alexey Dobriyan
2006-07-04 21:20   ` Petr Vandrovec
2006-07-05  2:47     ` Valdis.Kletnieks
2006-07-05  2:54       ` Petr Vandrovec [this message]

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=44AB29D3.9090106@vandrovec.name \
    --to=petr@vandrovec.name \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox