2.0.39 oopses in sys_new(l)stat

I wonder if there might still be a bug in 2.0.39 sys_new(l)stat. Today, one of my trustworthy servers crashed (see details below), and it has actually given me two slightly similar looking oopses before. While this might be a hardware problem (I'll run memory test asap), it seems that the oopses

Re: 2.0.39 oopses in sys_new(l)stat

On Thu, Apr 05, 2001 at 06:09:28PM +0300, Ville Herva wrote: > I wonder if there might still be a bug in 2.0.39 sys_new(l)stat. > Today, one of my trustworthy servers crashed (see details below), and > it has actually given me two slightly similar looking oopses before. > > While this might be a

2.0.39 stat/inode handling race? [2.0.39 oopses in sys_new(l)stat]

On Thu, Apr 05, 2001 at 11:34:46PM +0200, you [David Weinehall] claimed: > > I'll look into it. A note, however: the additional oops:es that follow > the first one are almost never ever useful, because the system is no > longer in a consistent state after the first one. Apr 5 05:33:35 some kern