> These oopses showed up on an otherwise idle 2.1.51 (one man one
> tin). Two very similar crond 2.1.50 oopses were reported here
> last week, I just want to stress the fact that this strangeness
> isn't gone in 2.1.51.
>
> The tin died trying to open(<tmp file>, O_RDWR|O_CREAT|O_EXCL, 0666)
> After a while every /usr/bin/clear trying to follow the symlink
> /usr/lib/terminfo oopsed on me, as well as any other attempt to
> act on the directory pointed to.
>
> After another couple of minutes, a /usr/bin/clear somehow looped
> in d_lookup, some sysrqs of that:
>
Sounds like a dentry got corrupted (landed on bad memory). It's happened to
me a couple of times, and I replaced some memory. <G> If userspace did
this, it would segfault, but the kernel can do anything it wants to.
-=- James Mastros