Subject: Re: Kernel BUG
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <Pine.LNX.4.10.10511031746300.3457-100000@mtfhpc.demon.co.uk>
References: <Pine.LNX.4.10.10511031746300.3457-100000@mtfhpc.demon.co.uk>
Content-Type: text/plain
Date: Thu, 03 Nov 2005 13:59:11 -0500
Message-Id: <1131044351.8830.6.camel@lade.trondhjem.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1146
Lines: 30

On Thu, 2005-11-03 at 18:10 +0000, Mark Fortescue wrote:
> Hi Trond,
> 
> I am running a sparc-linux kernel using an NFS Root and it is falling over
> with the trace below.
> 
> My Kernel is not a standard kernel (I have had to tweek it to get the
> SBUS GC3 and the 82077 floppy to work on my OPUS Sparc 1 clone).
> 
> Can you advise me on any known issues in the NFS Client code that might
> enter NULL pointers into the 'slot->slots[i]' in __lookup_tag.
> 
> If there are none that you are aware of, are there any specific areas that
> I should investigate with printk statements.

NFS does not ever directly access the radix tree internals: it always
uses the API, and it always protects those operations using the
NFS_I(inode)->req_lock.

Are you sure that radix_tree_init() is being called before the NFSroot
stuff is started? To me, this whole thing smells of memory scribble.

Cheers,
  Trond

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/