Nope. On my system (2.5.29-changeset548) it is a BUG() call which was
added by akpm in rmap.c revision 1.5, in his 'Add BUG() on a can't-happen
code path in page_remove_rmap()'. It just added #else BUG() branch
to #ifdef DEBUG_RMAP conditional.
Kernel is SMP, non-preempt, running on UP P4. Compiler is 2.95.4 from
Debian sid.
> > Stack trace:
> >
> > page_remove_rmap
> > zap_pte_range
> > zap_pmd_range
> > unmap_page_range
> > exit_mmap
> > mmput
> > do_exit
> > sys_exit
> > syscall_call
> >
> > If it is not known bug, I'll rebuild kernel with DEBUG_RMAP.
> > Unfortunately it looks like that machine must have uptime > 12hrs to
> > trigger this. Probably updatedb or some other task must be run to try to
> > swap ntpd out?
>
> It is not a known bug. In fact I've never seen this one before.
Probably because of your code did not do anything special when
'Not found. This should NEVER happen!' code path triggers. Code in
bitkeeper since 27th July complains. I'm now running with DEBUG_RMAP
set, so I'll see next time.
Petr Vandrovec
vandrove@vc.cvut.cz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/