public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: linux-kernel@vger.kernel.org
Cc: rgooch@atnf.csiro.au
Subject: Linux 2.4-bk: Kernel BUG at dcache.c:653
Date: Tue, 01 Apr 2003 16:08:06 +0100	[thread overview]
Message-ID: <3E89AB56.3080000@walrond.org> (raw)


On about 50% of reboots of a server, I get this BUG message while the 
kernel has just started processing my init script.

This is a dual P3 machine with DAC960 raid card.

I am running the latest 2.4-bk kernel

Any clues what might cause this? Since I am running Richard Gooch's 
simpleinit (with homebrew scripts) which does loads of init stuff in 
parallel, I'm sure they must be the cause.

Very early in the scripts, root is remounted ro and fscked, then 
remounted rw, while other parallel scripts wait on it to complete.

What does this BUG indicate? It occurs in this function:

/**
  * d_instantiate - fill in inode information for a dentry
  * @entry: dentry to complete
  * @inode: inode to attach to this dentry
  *
  * Fill in inode information in the entry.
  *
  * This turns negative dentries into productive full members
  * of society.
  *
  * NOTE! This assumes that the inode count has been incremented
  * (or otherwise set) by the caller to indicate that it is now
  * in use by the dcache.
  */

void d_instantiate(struct dentry *entry, struct inode * inode)
{
     if (!list_empty(&entry->d_alias)) BUG();
     spin_lock(&dcache_lock);
     if (inode)
         list_add(&entry->d_alias, &inode->i_dentry);
     entry->d_inode = inode;
     spin_unlock(&dcache_lock);
}


Andrew Walrond


                 reply	other threads:[~2003-04-01 14:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3E89AB56.3080000@walrond.org \
    --to=andrew@walrond.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@atnf.csiro.au \
    /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