linux-kernel - Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 19 Jul 2008 09:28:33 +0200
From:	Mariusz Kozlowski <m.kozlowski@...land.pl>
To:	Stephen Rothwell <sfr@...b.auug.org.au>,
	kernel-testers@...r.kernel.org
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller

Hello,

	I get this on my x86_32 laptop.

------------[ cut here ]------------
WARNING: at /home/mako/linux/lkt/sources/linux-next/kernel/lockdep.c:2068 trace_hardirqs_on_caller+0xdc/0x128()
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.26-next-20080718 #1
 [<c011d5ca>] warn_on_slowpath+0x4e/0x68
 [<c0132600>] ? init_srcu_struct+0x17/0x3b
 [<c011de86>] ? release_console_sem+0x1c2/0x1e8
 [<c0139818>] ? trace_hardirqs_off+0xb/0xd
 [<c02b95cb>] ? _spin_unlock_irqrestore+0x39/0x60
 [<c011de9a>] ? release_console_sem+0x1d6/0x1e8
 [<c01326be>] ? up+0x23/0x30
 [<c011de86>] ? release_console_sem+0x1c2/0x1e8
 [<c01326be>] ? up+0x23/0x30
 [<c011de86>] ? release_console_sem+0x1c2/0x1e8
 [<c013b83b>] ? __lock_acquire+0x365/0x1151
 [<c013b048>] trace_hardirqs_on_caller+0xdc/0x128
 [<c013b09f>] trace_hardirqs_on+0xb/0xd
 [<c016a40b>] __slab_alloc+0x329/0x61e
 [<c011665f>] ? kmemcheck_memset+0x24/0xe5
 [<c016a7a0>] kmem_cache_alloc+0xa0/0xb6
 [<c01dedb4>] ? kobject_init+0x3b/0xdd
 [<c01dedb4>] ? kobject_init+0x3b/0xdd
 [<c01dedb4>] kobject_init+0x3b/0xdd
 [<c025997f>] firmware_map_add_entry+0x2a/0x4b
 [<c03b8e0c>] firmware_map_add_early+0x32/0x56
 [<c03a3faf>] e820_reserve_resources+0x10a/0x14e
 [<c03a1965>] setup_arch+0x375/0x540
 [<c0136e81>] ? clockevents_register_notifier+0x28/0x2d
 [<c011e477>] ? printk+0x1b/0x1d
 [<c03a09df>] start_kernel+0x67/0x278
 [<c03a0304>] i386_start_kernel+0x64/0x70
 =======================
---[ end trace 4eaa2a86a8e2da22 ]---

and that's

/*
 * Hardirqs will be enabled:
 */
void trace_hardirqs_on_caller(unsigned long a0)
{
        struct task_struct *curr = current;
        unsigned long ip;

        time_hardirqs_on(CALLER_ADDR0, a0);

        if (unlikely(!debug_locks || current->lockdep_recursion))
                return;

------> if (DEBUG_LOCKS_WARN_ON(unlikely(!early_boot_irqs_enabled))) <------
                return;

        if (unlikely(curr->hardirqs_enabled)) {
                debug_atomic_inc(&redundant_hardirqs_on);
                return;


View attachment ".config" of type "text/plain" (42097 bytes)

View attachment "full-dmesg" of type "text/plain" (18885 bytes)