xfs
[Top] [All Lists]

Re: Bug submission?

To: ian.nelson@xxxxxxxxxxxx
Subject: Re: Bug submission?
From: cattelan@xxxxxxxxxxx
Date: Tue, 11 Apr 2000 13:58:01 -0500
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: In your message of "Tue, 11 Apr 2000 12:37:18 -0600" <38F370DE.6B35A30@xxxxxxxxxxxx>
References: <38F370DE.6B35A30@xxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Wanderlust/1.0.3 (Notorious) tm/7.108 XEmacs/21.1 (Bryce Canyon)
At Tue, 11 Apr 2000 12:37:18 -0600,
Ian S. Nelson <ian.nelson@xxxxxxxxxxxx> wrote:
> 
> 
> How do I submit bugs?
just send it to the list at the moment.

> I've been hammering on XFS and it works great until I export it and
> start hammering on it over NFS. It pretty regularly causes a kernel
> panic or some distortion of data.   Files aren't read properly, can't
> remove directories, things like that.  I suspect this may not be a
> "supported configuration"  yet but I was doing concurrent kernel
> compiles to stress it out and I wanted to do a few more, only CPU cycles
> were starting to be the limiting factor (thus NFS and another CPU seemed
> to make sense)  It seems like something is getting confused, perhaps NFS
> takes a short cut through the VFS layer that XFS doesn't know about or
> something like that.
> 
> pagebuf_get(..) is where the panic occurs, "kernel can't handle
> NULL pointer exception"
> 
> I looked at the pagebuf_get source and the first thing that jumped out
> to me was that the comment says ip can can be NULL but it's never
> checked to see if it's NULL, it's just dereferenced.  So that kind of
> looks like a bug,  I'm not familiar enough with the code to tell what
> the proper fix is though.   Just returning probably isn't the best
> solution.
> I put some printk statments  (if (ip==NULL) printk(...); ) in to try and
> pin down where it was but they never wrote anything out, it just drops
> into kdb.
> 
Send the back trace.
I'm probably chasing the same bug right now.

Where was this comment about ip possibly being null.




<Prev in Thread] Current Thread [Next in Thread>