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-next>] [day] [month] [year] [list]
Date:	Thu, 29 Nov 2007 15:25:46 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	linux-kernel@...r.kernel.org
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	"David S. Miller" <davem@...emloft.net>,
	Allan Stephens <allan.stephens@...driver.com>,
	Jon Paul Maloy <jon.maloy@...csson.com>
Subject: [bug] tipc_init(), WARNING: at arch/x86/mm/highmem_32.c:52
	kmap_atomic_prot()


i'm getting this on 32-bit (with the kmap-atomic debugging patch 
applied):

 ---------------->
 Calling initcall 0x78b67c00: tipc_init+0x0/0xc0()
 TIPC: Activated (version 1.6.2 compiled Nov 29 2007 15:04:36)
 WARNING: at arch/x86/mm/highmem_32.c:52 kmap_atomic_prot()
 Pid: 1, comm: swapper Not tainted 2.6.24-rc3-cfs-v24 #45
  [<78107272>] show_trace_log_lvl+0x12/0x40
  [<781072ad>] show_trace+0xd/0x20
  [<781086f8>] dump_stack+0x58/0x60
  [<7811541f>] kmap_atomic_prot+0x1bf/0x240
  [<781154ae>] kmap_atomic+0xe/0x20
  [<78157be5>] get_page_from_freelist+0x225/0x420
  [<78157e4d>] __alloc_pages+0x6d/0x3a0
  [<78169a7b>] slob_new_page+0x1b/0x60
  [<78169be4>] slob_alloc+0x124/0x1e0
  [<78169e0f>] __kmalloc_node+0x6f/0xa0
  [<7884f7c2>] reg_init+0x42/0x80
  [<7884f80a>] tipc_reg_start+0xa/0x40
  [<7883e6c6>] tipc_core_start+0x66/0xc0
  [<78b67c81>] tipc_init+0x81/0xc0
  [<78b32898>] kernel_init+0x158/0x260
  [<78106f57>] kernel_thread_helper+0x7/0x10
  =======================
 NET: Registered protocol family 30
 TIPC: Started in single node mode
 initcall 0x78b67c00: tipc_init+0x0/0xc0() returned 0.
 <------------------

the warning is due to:

        if (unlikely(in_interrupt())) {
                if (in_irq()) {
			...
                } else if (!irqs_disabled()) {  /* softirq */
                        if (type != KM_IRQ0 && type != KM_IRQ1 &&
                            type != KM_SOFTIRQ0 && type != KM_SOFTIRQ1 &&
                            type != KM_SKB_SUNRPC_DATA &&
                            type != KM_SKB_DATA_SOFTIRQ &&
                            type != KM_BOUNCE_READ) {
                                WARN_ON(1);

but it's not quite clear to me how we can be in a softirq context.

it seems quite reproducible - two bootups gave this warning.

	Ingo

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ