From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel BUG
Date: Thu, 03 Nov 2005 13:59:11 -0500 [thread overview]
Message-ID: <1131044351.8830.6.camel@lade.trondhjem.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10511031746300.3457-100000@mtfhpc.demon.co.uk>
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
next prev parent reply other threads:[~2005-11-03 18:59 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 18:10 Mark Fortescue
2005-11-03 18:59 ` Trond Myklebust [this message]
2005-11-03 23:15 ` Mark Fortescue
2005-11-04 10:08 ` Mark Fortescue
[not found] <200907311139.55095.christoph.thielecke@gmx.de>
2009-07-31 16:01 ` kernel bug Linus Torvalds
2009-07-31 16:26 ` Eric Paris
-- strict thread matches above, loose matches on Subject: below --
2008-09-10 20:35 Todor Gyumyushev
2008-09-11 3:21 ` Aaron Straus
2008-04-13 16:06 monte
2008-04-13 18:20 ` Jesper Juhl
2008-04-13 18:33 ` Alan Cox
2008-03-29 9:05 Olver Eduardo Ramos
2008-03-30 1:06 ` Rafael J. Wysocki
2007-09-19 21:43 Kernel bug Branislav Bozgai
2007-09-24 15:33 ` Mel Gorman
2007-08-19 18:33 kernel bug Costas Sismanis
2006-12-22 11:59 Kernel BUG Rudy Zijlstra
2006-12-22 13:42 ` Peter Zijlstra
2005-11-26 1:23 Kernel bug Vympel
2005-11-27 12:51 ` Hugh Dickins
2003-03-26 23:57 Kernel BUG Perez-Gonzalez, Inaky
2003-03-27 14:23 ` Hugh Dickins
2003-03-26 13:13 kasper_k_jensen
2003-01-25 22:56 Kernel bug Massimiliano C. - Uf0On|in3
2003-01-19 18:01 Christophe Dupre
2003-01-07 9:17 kernel BUG Sönke Ruempler
2002-12-07 10:09 Kernel BUG Henrik Steffen
2002-12-08 1:47 ` Alan Cox
2002-11-27 11:31 kernel bug sanket rathi
2002-11-27 10:45 sanket rathi
2002-11-27 9:50 sanket rathi
2002-11-27 10:10 ` Arjan van de Ven
2002-06-28 19:54 kernel BUG Eric Weiss
2002-06-28 19:26 ew
2002-06-27 19:23 Chaoyang Deng
2002-06-28 5:58 ` Austin Gonyou
2002-06-28 14:00 ` Mike Black
2002-05-21 14:01 kernel bug Chen Hao
2001-11-25 18:03 Kernel Bug gonzalo.ab
2001-11-25 23:59 ` Adam Schrotenboer
2001-03-06 19:55 kernel bug ernte23
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=1131044351.8830.6.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mtfhpc.demon.co.uk \
/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
all inboxes | Powered by JetHome®