linux-kernel - Re: 2.6.36-git4 -- BUG: looking up invalid subclass: 31 -- turning off the locking correctness validator.

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 25 Oct 2010 00:56:17 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Miles Lane <miles.lane@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Alessandro Rubini <rubini@...vis.unipv.it>
Subject: Re: 2.6.36-git4 -- BUG: looking up invalid subclass: 31 -- turning
 off the locking correctness validator.

Hi Miles,

On Sun, Oct 24, 2010 at 06:00:30PM -0400, Miles Lane wrote:
> BUG: looking up invalid subclass: 31
> turning off the locking correctness validator.
> Pid: 1, comm: swapper Not tainted 2.6.36-git4 #3
> Call Trace:
>  [<ffffffff810634a7>] look_up_lock_class+0x66/0xe6
>  [<ffffffff81063940>] register_lock_class+0x1e/0x30e
>  [<ffffffff81062d07>] ? trace_hardirqs_on+0xd/0xf
>  [<ffffffff81064f70>] lockdep_init_map+0xf9/0x10c
>  [<ffffffff812a949b>] mousedev_create+0xb3/0x1e7
>  [<ffffffff816a2afe>] ? mousedev_init+0x0/0x62
>  [<ffffffff816a2b1a>] mousedev_init+0x1c/0x62
>  [<ffffffff81000336>] do_one_initcall+0x7a/0x130
>  [<ffffffff8167ad1e>] kernel_init+0x148/0x1d2
>  [<ffffffff81003854>] kernel_thread_helper+0x4/0x10
>  [<ffffffff8102ea4f>] ? finish_task_switch+0x3f/0x9a
>  [<ffffffff813619c0>] ? restore_args+0x0/0x30
>  [<ffffffff8167abd6>] ? kernel_init+0x0/0x1d2
>  [<ffffffff81003850>] ? kernel_thread_helper+0x0/0x10

This should be fixed by:

commit f74eef95e33a07379aa2b950c7f313cbfd55ebbe
Author: Hitoshi Mitake <mitake@....info.waseda.ac.jp>
Date:   Wed Oct 13 11:35:40 2010 -0700

    Input: mousedev - correct lockdep annotation
    
    When annotating mutex to avoid false lockdep reports we should not
    be using MOUSEDEV_MIX as lock subclass but rather SINGLE_DEPTH_NESTING.
    
    Signed-off-by: Hitoshi Mitake <mitake@....info.waseda.ac.jp>
    Signed-off-by: Dmitry Torokhov <dtor@...l.ru>

once Linus pulls from my tree.

Thanks.

-- 
Dmitry
--
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/