From: Ingo Molnar <mingo@elte.hu>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Allan Stephens <allan.stephens@windriver.com>,
Jon Paul Maloy <jon.maloy@ericsson.com>,
Matt Mackall <mpm@selenic.com>
Subject: Re: [bug] SLOB, tipc_init(), WARNING: at arch/x86/mm/highmem_32.c:52 kmap_atomic_prot()
Date: Thu, 29 Nov 2007 15:39:20 +0100 [thread overview]
Message-ID: <20071129143920.GA32146@elte.hu> (raw)
In-Reply-To: <20071129142546.GA27719@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> 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
this is due to the kzalloc() here:
0x7884f1d0 is in reg_init (net/tipc/user_reg.c:88).
83 spin_lock_bh(®_lock);
84 if (!users) {
85 users = kzalloc(USER_LIST_SIZE, GFP_ATOMIC);
86 if (users) {
87 for (i = 1; i <= MAX_USERID; i++) {
88 users[i].next = i - 1;
which does a:
120 static inline void clear_highpage(struct page *page)
121 {
122 void *kaddr = kmap_atomic(page, KM_USER0);
123 clear_page(kaddr);
124 kunmap_atomic(kaddr, KM_USER0);
125 }
but ... why does the debug code think it's in softirq context?
plus, and this is a slob question i guess, how come we drop into
clear_highpage() for a kzalloc()??
Ingo
next prev parent reply other threads:[~2007-11-29 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 14:25 [bug] tipc_init(), WARNING: at arch/x86/mm/highmem_32.c:52 kmap_atomic_prot() Ingo Molnar
2007-11-29 14:39 ` Ingo Molnar [this message]
2007-11-29 20:00 ` [bug] SLOB, " Andrew Morton
2007-11-29 21:32 ` Matt Mackall
2007-11-30 9:14 ` Ingo Molnar
2007-11-30 22:35 ` Matt Mackall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071129143920.GA32146@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=allan.stephens@windriver.com \
--cc=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox