From: Tejun Heo <tj@kernel.org>
To: Ben Hutchings <ben@decadent.org.uk>,
Dave Jones <davej@redhat.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Rusty Russell <rusty@rustcorp.com.au>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: out-of-tree module shouldn't disable lockdep
Date: Thu, 22 Dec 2011 08:59:52 -0800 [thread overview]
Message-ID: <20111222165952.GH17084@google.com> (raw)
Hello, guys.
2449b8ba074 "module,bug: Add TAINT_OOT_MODULE flag for modules not
built in-tree" added TAINT_OOT_MODULE to mark kernel which has
out-of-tree module loaded, which might be a good idea but an
unfortunate side effect of tainting is that it disables lockdep. So,
now, none of my test modules is watched by lockdep. This is a bad bad
idea. People use oot modules to write test code and disabling lockdep
for test codes is silly. Can we please fix this?
Thanks.
--
tejun
next reply other threads:[~2011-12-22 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 16:59 Tejun Heo [this message]
2011-12-22 17:07 ` out-of-tree module shouldn't disable lockdep Tejun Heo
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=20111222165952.GH17084@google.com \
--to=tj@kernel.org \
--cc=ben@decadent.org.uk \
--cc=davej@redhat.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rusty@rustcorp.com.au \
/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.