On Fri, 16 Dec 2011 04:39:49 +, Ben Hutchings b...@decadent.org.uk wrote:
Non-text part: multipart/signed
On Fri, 2011-12-16 at 14:26 +1030, Rusty Russell wrote:
On Wed, 14 Dec 2011 11:20:03 -0500, John W. Linville
linvi...@tuxdriver.com wrote:
We really want to indicate out-of-support
On Wed, 14 Dec 2011 11:20:03 -0500, John W. Linville linvi...@tuxdriver.com
wrote:
In some cases, it might be desirable to package a module from an
external source tree alongside the base kernel. In those cases, it
might also be desirable to not have those modules tainting the kernel.
This
On Wed, 07 Dec 2011 14:30:58 +, Ben Hutchings b...@decadent.org.uk wrote:
We do want to allow lock debugging for GPL-compatible modules that are
not (yet) built in-tree. This was disabled as a side-effect of commit
2449b8ba0745327c5fa49a8d9acffe03b2eded69 ('module,bug: Add
lockdep and rtmutex-debug error messages.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
Acked-by: Rusty Russell ru...@rustcorp.com.au
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive
On Wed, 26 Oct 2011 21:55:28 -0400, Dave Jones da...@redhat.com wrote:
On Thu, Oct 27, 2011 at 11:41:37AM +1030, Rusty Russell wrote:
I think we need a taint_string() function, and instead of lockdep
disabling itself it should note the taint string in its reports.
Similarly
On Fri, 28 Oct 2011 04:38:14 +0100, Ben Hutchings b...@decadent.org.uk wrote:
Dynamic debugging was enabled for GPL-compatible out-of-tree modules
until my addition of TAINT_OOT_MODULE. It should continue to be
enabled now.
Please just remove the test entirely.
AFAICT there's nothing unique
On Mon, 31 Oct 2011 13:44:17 +, Ben Hutchings b...@decadent.org.uk wrote:
Non-text part: multipart/signed
On Mon, 2011-10-31 at 12:29 +1030, Rusty Russell wrote:
On Fri, 28 Oct 2011 04:38:14 +0100, Ben Hutchings b...@decadent.org.uk
wrote:
Dynamic debugging was enabled for GPL
On Tue, 01 Nov 2011 03:59:33 +, Ben Hutchings b...@decadent.org.uk wrote:
Dynamic debugging is currently disabled for tainted modules, except
for TAINT_CRAP. This prevents use of dynamic debugging for
out-of-tree modules now that they are also tainted.
This condition was apparently
On Wed, 26 Oct 2011 09:08:34 -0400, Nick Bowler nbow...@elliptictech.com
wrote:
On 2011-10-25 22:54 +0200, Greg KH wrote:
On Tue, Oct 25, 2011 at 04:17:24PM -0400, Dave Jones wrote:
On Tue, Oct 25, 2011 at 10:04:55PM +0200, Greg Kroah-Hartman wrote:
On Tue, Oct 25, 2011 at 12:51:42PM
On Tue, 25 Oct 2011 16:17:24 -0400, Dave Jones da...@redhat.com wrote:
commit 7816c45bf13255157c00fb8aca86cb64d825e878
Author: Roland Vossen rvos...@broadcom.com
Date: Thu Apr 7 11:20:58 2011 +0200
modules: Enabled dynamic debugging for staging modules
...
Signed-off-by:
consider staging modules to be suspect, and this
should also be true for out-of-tree modules which may receive very
little review.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
Reviewed-by: Dave Jones da...@redhat.com
Acked-by: Greg Kroah-Hartman gre...@suse.de
Signed-off-by: Rusty Russell ru
On Sat, 2005-11-05 at 19:48 +0100, Pozsar Balazs wrote:
On Sat, Nov 05, 2005 at 06:31:04PM +0100, Kay Sievers wrote:
I've got these messages several times on the experimental SUSE too,
but can't reproduce it so far, even without Rusty's patch to modprobe
they have disappeared. See here for
On Mon, 2005-10-31 at 19:53 +0100, Marco d'Itri wrote:
On Oct 29, Rusty Russell [EMAIL PROTECTED] wrote:
Please send complete log.
Here it is. I can reproduce the bug even with a script like:
while read m; do
/sbin/modprobe.real $m
done LIST
(Each command was logged
On Thu, 2005-10-27 at 10:10 +0200, Marco d'Itri wrote:
And then it fails for ehci-hcd too (which is not loaded at all).
Rusty, do you have other ideas for debugging?
I have reread the bug reports, and meditated on this issue some more.
This is a possibility I was aware of when I changed to code
On Fri, 2005-10-28 at 15:08 +0200, Marco d'Itri wrote:
On Oct 28, Rusty Russell [EMAIL PROTECTED] wrote:
The latter is the simplest option. Please try this patch (it will be in
the next release, too). If it seems to work, please ack.
No luck.
Please send complete log.
I might need
On Tue, 2005-10-18 at 15:38 +0200, Martin Wilck wrote:
Rusty Russell wrote:
Martin Wilck [EMAIL PROTECTED] wrote:
0. the module loading tool runs during boot with PID 1.
I do not understand how this can happen. request_module() cannot occur
until usermodehelper_init() is called
On Thu, 2005-10-13 at 23:07 +0200, Marco d'Itri wrote:
Any comments?
Martin Wilck [EMAIL PROTECTED] wrote:
0. the module loading tool runs during boot with PID 1.
I do not understand how this can happen. request_module() cannot occur
until usermodehelper_init() is called. This is only done
On Sun, 2005-10-09 at 16:26 +0200, Kay Sievers wrote:
On Sun, Oct 09, 2005 at 10:56:15AM +0200, Marco d'Itri wrote:
What do you think about this? It happens when udevd tries to load a
dozen of modules at boot time. Is there a race in modules loading?
It happens less frequently with other
around environment variables
Status: Tested on 2.6.9-rc2-bk13
Signed-off-by: Rusty Russell [EMAIL PROTECTED]
As noticed by Joey Hess (and thanks for Christoph for forwarding it):
if we decide that a command line option is not really for the kernel,
we turn it into an init command line arg or env
19 matches
Mail list logo
