linux-kernel - Re: linux-next: Tree for July 20 (lockdep warning)

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 21 Jul 2011 13:25:52 -0400
From:	Arnaud Lacombe <lacombar@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for July 20 (lockdep warning)

Hi,

On Wed, Jul 20, 2011 at 4:00 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
Not sure which tree is involved, but booting a kernel with qemu
triggers the following warning:

WARNING: at kernel/lockdep.c:2529 trace_hardirqs_on_caller+0x52/0x79()
Hardware name: Bochs
Modules linked in:
Pid: 1, comm: swapper Not tainted 3.0.0-rc7-next-20110720+ #3
Call Trace:
 [<c101bcfd>] warn_slowpath_common+0x65/0x7a
 [<c103da0d>] ? trace_hardirqs_on_caller+0x52/0x79
 [<c11df84c>] ? restore_all+0xf/0xf
 [<c10137a8>] ? vmalloc_sync_all+0x95/0x95
 [<c101bd21>] warn_slowpath_null+0xf/0x13
 [<c103da0d>] trace_hardirqs_on_caller+0x52/0x79
 [<c10be180>] trace_hardirqs_on_thunk+0xc/0x10
 [<c103efb0>] ? cmpxchg_futex_value_locked+0x3d/0x4f
 [<c11df84c>] ? restore_all+0xf/0xf
 [<c10137a8>] ? vmalloc_sync_all+0x95/0x95
 [<c11e0615>] ? iret_exc+0x345/0x984
 [<c143b68f>] ? start_kernel+0x28e/0x28e
 [<c14477d6>] ? futex_init+0x16/0x64
 [<c143b68f>] ? start_kernel+0x28e/0x28e
 [<c1001126>] ? do_one_initcall+0x70/0x11a
 [<c14477c0>] ? lockdep_proc_init+0x67/0x67
 [<c143b68f>] ? start_kernel+0x28e/0x28e
 [<c143b6ff>] ? kernel_init+0x70/0xe9
 [<c11e023a>] ? kernel_thread_helper+0x6/0xd

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