From: Andrew Morton <akpm@osdl.org>
To: pinotj@club-internet.fr
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Oops] i386 mm/slab.c (cache_flusharray)
Date: Wed, 19 Nov 2003 17:07:53 -0800 [thread overview]
Message-ID: <20031119170753.06ba5fb2.akpm@osdl.org> (raw)
In-Reply-To: <mnet1.1069265993.8009.pinotj@club-internet.fr>
pinotj@club-internet.fr wrote:
>
> kernel BUG at mm/slab.c:1957!
> invalid operand: 0000 [#1]
> CPU: 0
> EIP: 0060:[free_block+336/752] Not tainted
> EIP: 0060:[<c015ad40>] Not tainted
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010096
> eax: 00000045 ebx: 00000006 ecx: c0693854 edx: c056e4f8
> esi: cd09a000 edi: cd09a018 ebp: cf821c68 esp: cf821c3c
> ds: 007b es: 007b ss: 0068
> Stack: c0502240 c0502e1d cd09af18 c0652a00 00000001 0000003a cd09af18 0000000f
> cffdef08 c4bcd180 00000010 cf821ca0 c015afba cffed800 cffdef08 00000010
> 00000282 c1161ca0 00000000 00000001 cffee730 00000010 00010c00 c4bcd180
> Call Trace:
> [<c015afba>] cache_flusharray+0xda/0x2b0
> [<c015b7ad>] kmem_cache_free+0x1ad/0x3a0
> [<c018158c>] free_buffer_head+0x2c/0x60
> [<c018158c>] free_buffer_head+0x2c/0x60
urgh, there are several reports of this and it's always the buffer_head
slab. The code in there is trivial so perhaps it's just that the large
number of buffer_heads makes them a fat target.
You should have also seen the message "slab: double free detected in cache
'buffer_head', objp 0xNNNNNNNN".
Don't know, sorry.
next prev parent reply other threads:[~2003-11-20 1:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 18:19 [Oops] i386 mm/slab.c (cache_flusharray) pinotj
2003-11-20 1:07 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-20 1:50 pinotj
2003-11-20 2:09 ` Andrew Morton
2003-11-21 18:12 pinotj
2003-11-21 18:58 ` Manfred Spraul
2003-11-22 7:47 Re: " pinotj
2003-11-22 10:55 ` Manfred Spraul
2003-11-25 17:30 pinotj
2003-11-25 22:51 ` Linus Torvalds
2003-11-27 18:07 ` Manfred Spraul
2003-11-27 18:42 pinotj
2003-11-27 18:55 ` Manfred Spraul
2003-12-02 1:03 ` Mike Fedyk
2003-11-29 17:41 pinotj
2003-12-02 0:36 ` Linus Torvalds
2003-12-02 1:37 ` Nathan Scott
2003-12-02 6:44 ` Nathan Scott
2003-12-02 18:05 ` Mike Fedyk
2003-12-02 20:05 ` Nathan Scott
2003-12-03 23:06 pinotj
2003-12-03 23:26 ` Linus Torvalds
2003-12-04 18:27 pinotj
2003-12-04 18:49 ` Linus Torvalds
2003-12-04 19:09 ` Linus Torvalds
2003-12-04 21:21 ` Nathan Scott
2003-12-05 7:14 ` Christoph Hellwig
2003-12-05 9:34 ` Nathan Scott
2003-12-05 14:22 ` Christoph Hellwig
2003-12-05 3:00 ` Nathan Scott
2003-12-05 6:40 ` Linus Torvalds
2003-12-04 19:19 ` Manfred Spraul
2003-12-04 21:26 ` Nathan Scott
2003-12-09 0:57 pinotj
2003-12-09 2:03 ` Nathan Scott
2003-12-09 7:21 ` Christoph Hellwig
2003-12-09 23:58 ` Nathan Scott
2003-12-12 19:00 ` Christoph Hellwig
2003-12-12 20:07 ` Manfred Spraul
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=20031119170753.06ba5fb2.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pinotj@club-internet.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.