Could you file a bug in bugzilla about this, so it doesn't get
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
> but it is locked after a while, I studied all the process trace of the
> it seems that only one process is locked, the trace is here.
> (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)
> 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
> 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!?
> [[HTML alternate version deleted]]