From: Andrew Morton <akpm@digeo.com>
To: khromy <khromy@lnuxlab.ath.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.53-mm2: scheduling while atomic! + kernel BUG at mm/slab.c:1671!
Date: Mon, 30 Dec 2002 16:11:27 -0800 [thread overview]
Message-ID: <3E10E0AF.9342B1D7@digeo.com> (raw)
In-Reply-To: 20021231001518.GA28259@lnuxlab.ath.cx
khromy wrote:
>
> Running 2.5.53-mm2 I got the following in dmesg. I have no idea how to
> reproduce them since I wasn't here when they occured..
>
> bad: scheduling while atomic!
This one is the bug in pte_chain_alloc(). It _should_ look like
this:
struct pte_chain *pte_chain_alloc(int gfp_flags)
{
int cpu;
struct pte_chain *ret;
struct pte_chain **pte_chainp;
cpu = get_cpu();
pte_chainp = &per_cpu(local_pte_chain, cpu);
if (*pte_chainp) {
ret = *pte_chainp;
*pte_chainp = NULL;
put_cpu();
} else {
put_cpu();
ret = kmem_cache_alloc(pte_chain_cache, gfp_flags);
}
return ret;
}
> kernel BUG at mm/slab.c:1671!
> invalid operand: 0000
> CPU: 0
> EIP: 0060:[<c012d2eb>] Not tainted
> EFLAGS: 00010a02
> EIP is at kmalloc+0xbb/0x114
> eax: c3ff9518 ebx: cffff440 ecx: 00000000 edx: cfff3bc3
> esi: cfff3b40 edi: cfff3b40 ebp: c360f1f4 esp: c6367e70
> ds: 007b es: 007b ss: 0068
> Process find (pid: 1563, threadinfo=c6366000 task=c3e326e0)
> Stack: c1546364 cc3a28f4 cc3a295c c01517ec 00000070 000001d0 00000000 cc3a28f4
> cc3a295c c360f1f4 00000066 c01492fc c360f1f4 c6367f14 00000000 c6367f54
> cfff7324 c6367f14 c01495a0 c360f1f4 c6367f14 00000004 c6367f0c 00000000
> Call Trace:
> [<c01517ec>] d_alloc+0x48/0x194
> [<c01492fc>] real_lookup+0x38/0xc0
This means that someone altered a dentry after freeing it. Could
be a problem in the new dcache_rcu code, or it could be a random
memory scribble. hmm.
next prev parent reply other threads:[~2002-12-31 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 0:15 2.5.53-mm2: scheduling while atomic! + kernel BUG at mm/slab.c:1671! khromy
2002-12-31 0:11 ` Andrew Morton [this message]
[not found] ` <20021231151738.C13443@in.ibm.com>
2002-12-31 16:33 ` khromy
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=3E10E0AF.9342B1D7@digeo.com \
--to=akpm@digeo.com \
--cc=khromy@lnuxlab.ath.cx \
--cc=linux-kernel@vger.kernel.org \
/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