xfs
[Top] [All Lists]

Re: the cvs kernel oops !!

To: tom wang <wddi_1976@xxxxxxxxxxxx>
Subject: Re: the cvs kernel oops !!
From: Russell Cattelan <cattelan@xxxxxxxxxxx>
Date: 13 Nov 2002 12:02:39 -0600
Cc: Eric Sandeen <sandeen@xxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <20021113030224.57610.qmail@web15202.mail.bjs.yahoo.com>
References: <20021113030224.57610.qmail@web15202.mail.bjs.yahoo.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
Could you file a bug in bugzilla about this, so it doesn't get
lost.
http://oss.sgi.com/bugzilla/

Probably a candidate for 1.2 
On Tue, 2002-11-12 at 21:02, tom wang wrote:
> 
>  Just now, I tried that test on the  cvs kernel again, it did not oops 
> anymore,
> but it is locked after a while, I studied all the process trace of the 
> system, 
> it seems that only one process is locked, the trace is here.
> __down()
> __down_failed()
> [xfs].text.lock.xfs_log
> xlog_state_get_iclog_space()
> xlog_write()
> xfs_log_write()
> xfs_trans_commit()
> xfs_attr_rolltrans£¨£©
> xfs_attr_mode_addname()
> xfs_attr_set()
> linvfs_setxattr()
> setxattr()
> sys_lsetxattr()
> system_call()
> (It seems that some process was wirting the log to disk. but no other process 
> was writing to disk at this time)
> I think it is easy reproduce in your box. (BTW if we compiled xfs with DEBUG 
> option, the xfsidbg module can not been installed)
> thanks.
>                                                       tom
>  
>  
>  
>  
>  
>  
>  
>  
>   Eric Sandeen <sandeen@xxxxxxx> µÄÕýÎÄ£º As another datapoint, Christoph and 
> I both tried it with ext3 on 2.5.47,
> and could not reproduce it. Also, could not reproduce it as a non-root
> user.
> 
> -Eric
> 
> On Tue, 2002-11-12 at 17:17, Christoph Hellwig wrote:
> > On Tue, Nov 12, 2002 at 06:27:15PM +0800, tom wang wrote:
> > > fsstress is the program provided in xfstest package.
> > > the kernel I used is now cvs kernel. 
> > > 
> > > the oops is easy reproduce, so maybe you can fix it
> > 
> > I could reproduce it here, too. The trace I got made no sense at
> > all, though and when I put in a bunch of debug printks I got a very
> > different oops output. After fixing the unchecked malloc today
> > I couldn't reproduce it anymore. Can you please test the latest
> > CVS tree?
> > 
> -- 
> Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
> sandeen@xxxxxxx SGI, Inc. 651-683-3102
> 
> 
> 
> ---------------------------------
> Do You Yahoo!?
> "ÊÇIT¾«Ó¢Âð£¿Ð¡ÊÔÅ£µ¶»ñʱÉд󽱣¡"
> 
> [[HTML alternate version deleted]]
> 
> 




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