From: Walt H <waltabbyh@comcast.net>
To: maneesh@in.ibm.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.1-mm2: BUG in kswapd?
Date: Fri, 16 Jan 2004 08:00:24 -0800 [thread overview]
Message-ID: <40080A98.4080105@comcast.net> (raw)
In-Reply-To: <20040116102211.GC1276@in.ibm.com>
Maneesh Soni wrote:
> On Fri, Jan 16, 2004 at 03:10:37PM +0530, Maneesh Soni wrote:
>
> [..]
>
>>Can you elaborate on the recreation scenario a little bit more or if possible
>>run this debug patch on top of -mm3. This should print some info about the
>>bad dentry.
>>
>
>
>
> Walt,
>
> Pleae run this debug patch instead of the previous one. Thanks to Andrew
> for suggestion.
>
>
> fs/dcache.c | 6 ++++++
> 1 files changed, 6 insertions(+)
>
> diff -puN fs/dcache.c~prune_dcache-debug fs/dcache.c
> --- linux-2.6.1-mm3/fs/dcache.c~prune_dcache-debug 2004-01-16 14:36:00.000000000 +0530
> +++ linux-2.6.1-mm3-maneesh/fs/dcache.c 2004-01-16 15:41:26.000000000 +0530
> @@ -344,6 +344,12 @@ static inline void prune_one_dentry(stru
> struct dentry * parent;
>
> __d_drop(dentry);
> + if (dentry->d_child.next->prev != &dentry->d_child) {
> + printk("Bad dentry for %s count %d %p %p\n", dentry->d_name.name, atomic_read(&dentry->d_count), dentry->d_child.next, dentry->d_child.prev);
> + if (dentry->d_sb)
> + printk("Super block magic %lx\n", dentry->d_sb->s_magic);
> + BUG();
> + }
> list_del(&dentry->d_child);
> dentry_stat.nr_dentry--; /* For d_free, below */
> dentry_iput(dentry);
>
> _
>
OK. I've got -mm3 with this debug patch running now. Hopefully this will
give us more info.
My workload that causes this bug most readily to appear is:
Use the computer system for a few hours. Compile some apps, surf, email
etc... At the end of the day, I typically shut down the system to
runlevel 1 to back it up. I've got a 2 disk md raid0 array that is my
primary working array, which I then backup to a 2 disk device mapper
raid0 array. An rsync from the primary to the secondary usually trips
the bug. If I boot the system and immediately do the rsync, it will
complete. It takes a period of uptime to trigger.
I've got a rather lengthy compile process now, so will try the rsync
after work and report on any debug success (rsync failures). Thanks,
-Walt
next prev parent reply other threads:[~2004-01-16 16:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 16:03 Oops in kobject_put during rsync backup on 2.6.2-rc1-mm3 Walt H
2004-01-16 4:05 ` 2.6.1-mm2: BUG in kswapd? Walt H
2004-01-16 9:40 ` Maneesh Soni
2004-01-16 10:03 ` Maneesh Soni
2004-01-16 10:22 ` Maneesh Soni
2004-01-16 16:00 ` Walt H [this message]
[not found] ` <20040128111333.GA2990@in.ibm.com>
2004-01-28 15:53 ` 2.6.1-mm2: BUG in kswapd? / Oops in kobject_put during rsync Walt H
-- strict thread matches above, loose matches on Subject: below --
2004-01-12 4:50 2.6.1-mm2: BUG in kswapd? Walt H
2004-01-11 17:33 Jan Ischebeck
2004-01-11 22:21 ` Max Valdez
2004-01-12 12:00 ` Maneesh Soni
2004-01-12 12:40 ` Jan Ischebeck
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=40080A98.4080105@comcast.net \
--to=waltabbyh@comcast.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.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 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.