From: Manfred Spraul <manfred@colorfullife.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Paul Larson <plars@linuxtestproject.org>, linux-mm <linux-mm@kvack.org>
Subject: Re: Hangs in 2.5.41-mm1
Date: Thu, 10 Oct 2002 20:39:06 +0200 [thread overview]
Message-ID: <3DA5C94A.5040508@colorfullife.com> (raw)
In-Reply-To: <3DA5B277.B5BFC9C0@digeo.com>
Andrew Morton wrote:
> Andrew Morton wrote:
>
>>...
>>#0 0xc01357c7 in cache_alloc_refill (cachep=0xf7ffc740, flags=464) at mm/slab.c:1580
>>#1 0xc0135b1a in kmem_cache_alloc (cachep=0xf7ffc740, flags=464) at mm/slab.c:1670
>>#2 0xc0159c72 in alloc_inode (sb=0xf7f8a400) at fs/inode.c:99
>>#3 0xc015a3c5 in new_inode (sb=0xf7f8a400) at fs/inode.c:505
>>#4 0xc014f7ae in get_pipe_inode () at fs/pipe.c:510
>>#5 0xc014f867 in do_pipe (fd=0xf6693fb4) at fs/pipe.c:559
>>#6 0xc010ce01 in sys_pipe (fildes=0xbffff83c) at arch/i386/kernel/sys_i386.c:35
>>#7 0xc01070f3 in syscall_call () at net/sunrpc/stats.c:204
>
>
> Or it could be that the inode cache has been corrupted.
> Bill, can you review the handling in there? It'd be a
> bit sad if one of the hugetlb privately-kmalloced inodes
> were put back onto the inode_cachep slab somehow.
Could you try to reproduce with slab debugging enabled? slab checks for
foreign objects and BUG's.
--
Manfred
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
prev parent reply other threads:[~2002-10-10 18:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 18:36 Paul Larson
2002-10-09 20:17 ` Andrew Morton
2002-10-09 20:29 ` Paul Larson
2002-10-09 21:00 ` William Lee Irwin III
2002-10-09 21:17 ` Paul Larson
2002-10-09 21:29 ` Andrew Morton
2002-10-09 21:32 ` Andrew Morton
2002-10-10 15:45 ` Paul Larson
2002-10-10 16:53 ` Andrew Morton
2002-10-10 17:01 ` Andrew Morton
2002-10-10 18:32 ` William Lee Irwin III
2002-10-10 18:39 ` Manfred Spraul [this message]
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=3DA5C94A.5040508@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@digeo.com \
--cc=linux-mm@kvack.org \
--cc=plars@linuxtestproject.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